Hi, And thank you all for your quick replies! I'm very embarrassed to say that I did indeed have a base class that had the Id property. I found it myself just minutes after posting this question. I guess I'll just email myself the questions from now on before posting them here. Alternatively I might have to set up some kind of sandbox forum software locally so I can get the full simulated experience before jumping the gun and posting. Sorry for this! Hopefully I might prevent someone else from making the same lame mistake. :-)
On Apr 8, 3:22 pm, Jon Kruger <[email protected]> wrote: > Are you deriving your entites from FluentHNibernate.Data.Entity? If so, > that class has an Id property on it, which would explain why the auto-mapper > is picking it up. If this is the case, then you probably shouldn't derive > from that Entity class. > > On Wed, Apr 8, 2009 at 6:32 AM, nuffsaid <[email protected]> wrote: > > > Hello, > > > This problem is a bit odd. I'll try to explain it as simple as > > possible. :-) > > > I'm using Automap, but overriding the Id column using IIdConvention > > because I want a different naming standard. This is working, but > > somehow I still get an Id column generated (as a normal property). My > > entities does not have a column named just "Id", but it still turns up > > in the mappings and in the generated schema. My entities look like > > this: > > > public class Foo > > { > > public Int64 FooId { get; private set; } > > } > > > Anyone know what is going on? How can I get rid of the generated "Id" > > column? Any help appreciated! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
