Hi Bryan, when a column has the same name as the table, it is renamed to "Contents". I tried removing this, but apparently, the DBML designer doesn't like when a column has the same name as its owner table.
So my best option for now is just to correct the renaming to use "Contents" everywhere, even in constraints. Pascal. On Fri, Sep 26, 2008 at 00:09, bryan costanich <[EMAIL PROTECTED]>wrote: > > they're all the same. > > i sent you a mySQL script to create a db that will repro it. > > perhaps the issue here is that the primary keys are named the same as > the table, e.g. "BoxOffice.BoxOffice" > > as the error would seem to indicate: Association > "BoxOffice_BoxOfficeEventAudit" references nonexistent property > "BoxOffice" on class "BoxOffice" > > perhaps? > > On Sep 25, 1:47 pm, "Pascal Craponne" <[EMAIL PROTECTED]> wrote: > > Are all errors the same?If yes, is there anything special about this > > constraint? This is probably something DbMetal doesn't catch. > > > > On Thu, Sep 25, 2008 at 22:42, bryan costanich <[EMAIL PROTECTED] > >wrote: > > > > > > > > > > > > > It generates now, but i'm getting a ton of errors when i drop the DBML > > > into visual studio. i'm getting a bunch of errors like these: > > > > > Error 1 Association "BoxOffice_BoxOfficeEventAudit" references > > > nonexistent property "BoxOffice" on class "BoxOffice" 0 > 0 > > > Error 2 Association "BoxOffice_BoxOfficeTerminal" references > > > nonexistent property "BoxOffice" on class "BoxOffice" 0 > 0 > > > Error 3 Association "BoxOffice_Event" references nonexistent > > > property > > > "BoxOffice" on class "BoxOffice" 0 0 > > > > > any ideas? > > > > > On Sep 25, 8:30 am, "Wayne Pedersen" <[EMAIL PROTECTED]> wrote: > > > > Good to know! > > > > I think this was the cause of much of my initial frustration with > DbLinq. > > > I > > > > will try to test it and see how it works out.... > > > > > > Wayne P. > > > > > > On Wed, Sep 24, 2008 at 4:57 PM, Pascal Craponne <[EMAIL PROTECTED]> > > > wrote: > > > > > > > This has just been fixed: DBML generation is working again. > > > > > > > Someone changed the adapters for associations and columns to lists, > so > > > > > the adapters weren't adapting anything anymore, and were working > for > > > > > themselves. > > > > > For people who want to know: it's on rev 892. > > > > > > > I strongly encourage DbMetal users to switch to latest revision. > > > > > > > Pascal. > > > > > > > On 24 sep, 20:39, "Pascal Craponne" <[EMAIL PROTECTED]> wrote: > > > > > > Hi everyone, > > > > > > due to some complaints here :), I took a look at DbMetal. > > > > > > And apparently, DBML generation is broken but C# code generation > > > works. > > > > > > > > This is probably not a big deal to fix, so I'll let you know here > how > > > > > things > > > > > > are progressing. > > > > > > > > Pascal. > > > > > > > > jabber/gtalk: [EMAIL PROTECTED] > > > > > > msn: [EMAIL PROTECTED] > > > > -- > > Pascal. > > > > jabber/gtalk: [EMAIL PROTECTED] > > msn: [EMAIL PROTECTED] > > > -- Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" 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/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
