|
May
15 |
|
awarded | Popular Question |
|
Apr
18 |
|
comment |
PostgreSQL Connection random errors This was the case. Devart maintained internal connection pool and had no recovery for an unexpected connection interruption. This as you say happened on a lower level than my code (probably in unmanaged code). I've managed to change Devart to NHibernate using the open source driver for PostgreSQL and at least a month ago this used to work. (I don't work there anymore) |
|
Apr
18 |
|
accepted | PostgreSQL Connection random errors |
|
Apr
11 |
|
comment |
Sorting tables by Master-Detail Relation Your way is definitely a good way to go if the schema can be modified. I had a requirement that schema must not be modified (this was a banking project, so my PM did not intend to take the risk of something going wrong with this solution). Another thing is: have you tested this for speed? |
|
Apr
11 |
|
comment |
Sorting tables by Master-Detail Relation Unfortunately I can't because I no longer have this code (I've changed work place). The solution can be coded in 15 minutes - query the tables and foreign keys, then sort the tables according to information from foreign keys. This does not work if the schema has cycles (eg. table A points to B and B points back to A, of course longer cycles will break things too). |
|
Apr
9 |
|
asked | Apps for Office - how to manipulate slide in Powerpoint |
|
Mar
22 |
|
comment |
NHibernate performing a delete with Cascade.All causes N+1 deletes Sorry I forgot that this was our extension method. It simply sets the KeyColumn to the appropriate value. |
|
Mar
22 |
|
accepted | NHibernate performing a delete with Cascade.All causes N+1 deletes |
|
Mar
21 |
|
revised |
NHibernate performing a delete with Cascade.All causes N+1 deletes added 83 characters in body |
|
Mar
21 |
|
awarded | Popular Question |
|
Mar
21 |
|
asked | NHibernate performing a delete with Cascade.All causes N+1 deletes |
|
Mar
20 |
|
awarded | Notable Question |
|
Mar
15 |
|
comment |
NHibernate Fetch when querying for single object Thanks for trying, but once again you totally missed the point. The question is not about writing another query, but about fixing it to work properly. That might be an NHibernate bug too. |
|
Mar
15 |
|
comment |
NHibernate Fetch when querying for single object This is a totally different query. You select Rights collection instead of selecting a profile with associated Rights. |
|
Mar
15 |
|
asked | NHibernate Fetch when querying for single object |
|
Mar
9 |
|
asked | FluentNHibernate - overriding already existing automappings |
|
Mar
6 |
|
awarded | Caucus |
|
Feb
1 |
|
comment |
Automapper mapping type with subtype Thanks for this solution although I have already solved this issue: using the ResolveUsing<>() and by creating a custom resolver. It has access to the parent entity as well as the child one.
|
|
Feb
1 |
|
asked | Automapper mapping type with subtype |
|
Jan
30 |
|
awarded | Notable Question |
