On Thu, 2010-08-19 at 13:20 -0700, sam wrote: > You lost me there, but then I am not a DB expert and I know virtually > nothing about dbml :)
I'm not DB expert either, and I forget most dbml details within days. > Can you provide a bit > more info on this catalog/schema thing you reference It's apparently an unstandardized figment of my imagination. The "best" explanation I can quickly find on Google: http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems#Databases_vs_Schemas_.28terminology.29 Basically, catalog/schema are a way of organizing database tables so that e.g. you can have the same table name mean different things in different schemas. Beyond that "organization" angle, the specifics appear to vary a lot between databases. That said, DbMetal already has a way to reduce the types that are generated: the --generate-type=TYPE parameter. Using this you could create the .dbml once, then only generate the types that you care about. This might not be a direct match for your requirements, but it already exists. :-) - Jon -- 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.
