This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I have a database with 2 schemas. In this database, I have two tables with the same name in both schemas. When I use the lsgen tool, just the table in the default schema is generated. Is it a bug? Thank you |
|
|
|
|
If you have a look at the output where it lists the files being generated you should see the file corresponding to that table name listed twice. lsgen writes out a new file for each instance of the table, so its a case of last out wins occurring. Before I make any changes, I am interested in your thoughts. Given you would have a class naming clash occuring if it was appending or creating a single file, what is your expectation on how it would deal with naming in this case.
|
|
|
|
|
Hi Jeremy, Thank you for being open to my ideas. I think an option in the arguments of the lsgen tool to indicate if we want each entity model class in a folder with the name of the schema would be nice. As example, if I have two schemas (Schema1 and Schema2), here is want I think would be nice: Folder Schema1
Folder Schema2
In this case, Table1 should be in the namespace ending with Schema2; CompanyName.ProjectName.Model.Schema2.Table1. For the argument of the lsgen tool, /fileStructure:folderBySchema and /fileStructure:default. Do you think it's a good idea? |
|
|
|
|
Thanks for the feedback. Ill largely implement this as you have suggested but if using a "bySchema" style I will also look for it to append the schema to the namespace to reflect the file structure and also to avoid a class name collision after generation. I will let you know once this has been updated in the nightlies.
|
|
|
|
