Hi Stefan, I came to the same conclusion. Our current AttributedMetaModel doesn't work dynamically, and it should (just like linq to sql does). The problem to be solved is that currently, the class reads all tables, then all associations between tables. The idea would be to merge the two steps so we can have a method that registers a table, its associations and related tables. I was planning to work on it soon, but let me know if you want to fix the code by yourself.
Pascal. On Thu, Oct 16, 2008 at 16:20, Stefan <[EMAIL PROTECTED]>wrote: > > Hi, > > I am just trying to get myself familiar with the dblinq codebase, > maybe I can then contribute some patches to make standalone > DataContext possible. > > Currently I think the main problem is how AttributedMetaModel > discovers the tables (reflection on the derived DataContext type > itself). > > Btw, the first message in this thread is from me, used the wrong > (test) account. > > > Stefan > > > -- 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 -~----------~----~----~----~------~----~------~--~---
