You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to add dynamic context to the Table and Columns to better define a data model for metadata.
When parsing is working can the unknown items be put in a dictionary to be accessed for other processes wishing to extend DBML.
example: Table ACCOUNT [note: "Account", description:"account", cdm_table: "account", generator: "<randomstring>"] { }
then when parsed this is available parsed.tables[0].settings["cdm_table"]
This would allow extension of the objects in the parser dynamically for arbitrary data that is not needed for database scripting.
The text was updated successfully, but these errors were encountered:
Although I'd only allow this with a special flag explicitly specified in the parser object, something like PyDBML('myfile.dbml', allow_extra=True), with allow_extra being False by default. Otherwise we could break compatibility for the future DBML syntax versions.
I would like to add dynamic context to the Table and Columns to better define a data model for metadata.
When parsing is working can the unknown items be put in a dictionary to be accessed for other processes wishing to extend DBML.
example:
Table ACCOUNT [note: "Account", description:"account", cdm_table: "account", generator: "<randomstring>"] { }
then when parsed this is available
parsed.tables[0].settings["cdm_table"]
This would allow extension of the objects in the parser dynamically for arbitrary data that is not needed for database scripting.
The text was updated successfully, but these errors were encountered: