I've been able to manually "marry up" Fluent NHibernate with
NHibernate 2.1 (a long involved process that already exceeds 5 pages
of steps). Even after doing so this issue remained until I changed
storemap.cs to this:
namespace Examples.FirstProject.Mappings
{
public class StoreMap : ClassMa
Bless you all for making this library - I love it.
I'm experiencing this same problem. The many-to-many seems to be
working fine, but not the one-to-many
On Mar 4, 7:57 am, x97mdr wrote:
> Ha! If it can be fixed that would be great, any help is much
> appreciated.
>
> ... and thanks for taking
Ha! If it can be fixed that would be great, any help is much
appreciated.
... and thanks for taking the time to do this project in the first
place. Making open source software is a labor of love! It needs some
recognition once in a while so here's the recognition :)
On Mar 3, 5:54 pm, James Gr
Take the lack of a response as an acknowledgement of the bug. I need not
reminding about it's existence, just the time to fix it.
On Tue, Mar 3, 2009 at 9:24 PM, fmorriso wrote:
>
> FYI: still not fixed using the latest Fluent NHibernate code (last
> modified Feb 26, 2009).
>
> On Feb 18, 6:48 p
Eric: It's mandatory if you want the child to be saved when saving the
parent; hence the cascading. It's not mandatory if you save the children
yourself.
On Tue, Mar 3, 2009 at 10:39 PM, Eric Liprandi wrote:
>
> FYI,
>
> I get the same (mis)behavior on SQL 2005. So I don't believe it's an
> issue
FYI,
I get the same (mis)behavior on SQL 2005. So I don't believe it's an
issue with the DB back-end.
I did notice that adding .Cascade.All() to the StoreMap class like
that:
HasMany(x => x.Staff)
.Cascade.All()
.Inverse();
Though I am new to the whole Fluent NHib
FYI: still not fixed using the latest Fluent NHibernate code (last
modified Feb 26, 2009).
On Feb 18, 6:48 pm, x97mdr wrote:
> *bump*
>
> Just wondering if this issue was ever resolved?
>
> On Feb 15, 3:30 pm, fmorriso wrote:
>
>
>
> > For what it's worth, here's the code for my temporary work-
No, the issue is still unresolved. I just pulled down the latest
Fluent NHibernate code and tried the example again and it did not
INSERT any records into table dbo.Employee when saving a new Store
object into table dbo.Store. The workaround is still needed (save any
unsaved Employee objects BEF
*bump*
Just wondering if this issue was ever resolved?
On Feb 15, 3:30 pm, fmorriso wrote:
> For what it's worth, here's the code for my temporary work-around.
> Put it after this line in Program.cs:
>
> var joan = new Employee { FirstName = "Joan", LastName = "Pope" };
>
>
For what it's worth, here's the code for my temporary work-around.
Put it after this line in Program.cs:
var joan = new Employee { FirstName = "Joan", LastName = "Pope" };
// added by Fred Morrison because Store objects
don't seem to save the Employee's
//
FYI: If I collect the Employee object instances into a List
and iterate through them via foreach loop and call SaveOrUpdate
method, the INSERT's into dbo.[Employee] occur. Later on, when the
example code saves the Store objects, it also generates corresponding
UPDATE EMPLOYEE ... SET Store_Id ..
Somebody else just raised this exact issue today, I'll investigate asap.
Thanks.
On Thu, Feb 12, 2009 at 9:20 PM, fmorriso wrote:
>
> I'm running the Examples.FirstProject using Microsoft SQL Server 2008
> Developer Edition and Visual Studio 2008 SP1, .Net Framework 3.5 SP1
> and it does not gen
12 matches
Mail list logo
