I was unaware that ever worked, but I've created an
issue<http://code.google.com/p/fluent-nhibernate/issues/detail?id=159>and
will investigate.
As for the site, it's up and has been all day.
On Mon, Mar 23, 2009 at 7:52 PM, Hitt <achar...@gmail.com> wrote:
>
> Before the conventions rewrite, the following two classes would map
> correctly:
>
> public class Example1
> {
> //....properties...
>
> public IList<Example2> Example2s {get; set;}
>
> }
>
> public class Example2
> {
> //....properties...
>
> public IList<Example1> Example1s {get; set;}
>
> }
>
> with this setup under the old code, a many to many would be created on
> both ends, with one side getting Inverse()d
>
> However, the new code doesn't seem to map this correctly, it
> essentially creates two identical mappings, with the table name being
> reversed on each side (That is, you'd have a Example1ToExample2 table,
> AND a Example2ToExample1 table)
>
> The old code would check to see which side was inversed, and get the
> table name appropriately, but the new architecture doesn't handle
> this.
>
> Also, when is the FluentNHibernate.org site going to be back up?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate@googlegroups.com
To unsubscribe from this group, send email to
fluent-nhibernate+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/fluent-nhibernate?hl=en
-~----------~----~----~----~------~----~------~--~---
