On Aug 19, 3:39 pm, Jonathan Pryor <[email protected]> wrote:
> > Q1: Is there some 3rd party tool that will read in the dbml and allow > > me to delete the tables I don't want in the dbml files? > > Any XML editor should work. ;-) That is assuming the human understands the in's and out's of dbml. I was hoping for some special tool that would simply list all the table names and when I deleted a bunch of them it would know how to remove all the references correctly so the dbml will remain valid. > > Q2: Has there ever been any thought and/or discussion on adding an -- > > includetable or --excludetable option to dbmetal? > > Not particularly. I suspect using separate catalogs/schemas is the > normal answer to this kind of problem. You lost me there, but then I am not a DB expert and I know virtually nothing about dbml :) Here is what I do know: I went in and hacked the select statements in the dbmetal code to limit the tables which came back from the provider (in my case that is Firebird). What I discovered was that I had to put effectively the same where clause on the select statements which returns the table, column, and associations. But once I had all three covered, it worked like a charm. So it is clear that limiting the scope is pretty easy to do, the only question is how best to implement the feature. Can you provide a bit more info on this catalog/schema thing you reference, I would like to evaluate that compared to the file with table names approach. Sam -- 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.
