| Key: |
NH-616
|
| Type: |
Task
|
| Status: |
Open
|
| Priority: |
Trivial
|
| Assignee: |
Unassigned
|
| Reporter: |
Sergey Koshcheyev
|
| Votes: |
0
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
NHibernate
Created: 29/May/06 02:22 AM
Updated: 26/Mar/08 10:53 PM
|
|
| Component/s: |
Core
|
| Affects Version/s: |
None
|
| Fix Version/s: |
LATER
|
|
|
Issue Links:
|
Related
|
|
This issue is related to:
|
|
|
NH-1266 ISQLExceptionConverter for various Dialects
|
|
|
|
|
|
This issue is related to:
|
|
|
|
|
 |
NH-387
Rolling back identifiers
|
|
|
|
|
|
|
|
|
|
|
NH-617
Add support for projections in criteria queries
|
|
|
|
|
|
NH-268
"not-found" attribute on relation mappings
|
|
|
|
|
|
|
|
|
|
|
NH-568
year(), month(),date() and some other functions: not supported in HQL
|
|
|
|
|
|
NH-606
Throw an meaningfull exception when collectionType.GetGenericArguments() returns 0 arguments.
|
|
|
|
|
|
NH-372
Allow insert="false", update="false" for components
|
|
|
|
|
|
NH-575
Enhance user types support
|
|
|
|
|
NH-633
Add support for generic collections to hbm2net
|
|
|
|
|
|
|
|
This issue contains links to NHibernate tasks somebody could work on who wants to contribute code to NHibernate but is not yet familiar with its internals. This means that either the task is downright easy, or it requires some work, but I have thought it out and have a clear idea of how to implement it, so I can provide guidance.
The main requirement for any submitted patches is that the code should follow Hibernate 3.x if it has a similar feature, unless there is a strong enough reason for doing things in a different way.
In general, fixing bugs or doing something platform-specific is a strong reason, while just implementing a feature differently because you could not be bothered to look at the Hibernate code is not.
|
|
Description
|
This issue contains links to NHibernate tasks somebody could work on who wants to contribute code to NHibernate but is not yet familiar with its internals. This means that either the task is downright easy, or it requires some work, but I have thought it out and have a clear idea of how to implement it, so I can provide guidance.
The main requirement for any submitted patches is that the code should follow Hibernate 3.x if it has a similar feature, unless there is a strong enough reason for doing things in a different way.
In general, fixing bugs or doing something platform-specific is a strong reason, while just implementing a feature differently because you could not be bothered to look at the Hibernate code is not. |
Show » |
|
