eg:
// define relationships - focus on “source” and “target”
// “source_type” and “target_type” is extra data used to selectively
truncate data set
var _data = [
{“source”: “Account”, “target_type”: “Master”, “target”: “Cost
Center”, “source_type”: “Master”},
{“source”: “Account”, “target_type”: null, “target”: “GL Entry”,
“source_type”: “Master”},
{“source”: “Account”, “target_type”: null, “target”: “Journal
Voucher”, “source_type”: “Master”},
{“source”: “Account”, “target_type”: “Master”, “target”: “Mode of
Payment”, “source_type”: “Master”},
Is there a data dictionary in the database somewhere that describes
the relationships between database tables and describing relation type
eg: 1 to many; many to many etc…
In addition are there any diagrams showing the tables layed out using
a err diagramming tool like “mysql-workbench”
I would like to contribute to the project some of the systems we have
developed for our internal accounting over the years and teh ER
Diagram is
absolutely necessary to be an effective contributor.
eg: // define relationships - focus on "source" and "target" // "source_type" and "target_type" is extra data used to selectively truncate data set var _data = [ {"source": "Account", "target_type": "Master", "target": "Cost Center", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "GL Entry", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "Journal Voucher", "source_type": "Master"}, {"source": "Account", "target_type": "Master", "target": "Mode of Payment", "source_type": "Master"},
Is there a data dictionary in the database somewhere that describes the relationships between database tables and describing relation type eg: 1 to many; many to many etc...
In addition are there any diagrams showing the tables layed out using a err diagramming tool like "mysql-workbench"
I would like to contribute to the project some of the systems we have developed for our internal accounting over the years and teh ER Diagram is absolutely necessary to be an effective contributor.
eg: // define relationships - focus on "source" and "target" // "source_type" and "target_type" is extra data used to selectively truncate data set var _data = [ {"source": "Account", "target_type": "Master", "target": "Cost Center", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "GL Entry", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "Journal Voucher", "source_type": "Master"}, {"source": "Account", "target_type": "Master", "target": "Mode of Payment", "source_type": "Master"},
Is there a data dictionary in the database somewhere that describes the relationships between database tables and describing relation type eg: 1 to many; many to many etc...
In addition are there any diagrams showing the tables layed out using a err diagramming tool like "mysql-workbench"
I would like to contribute to the project some of the systems we have developed for our internal accounting over the years and teh ER Diagram is absolutely necessary to be an effective contributor.
The table relationships are exactly same as DocTypes. Every time a DocType is saved, the schema is updated. You can get a better idea by browsing DocTypes. If you are logged in as Administrator, go to #List/DocType in the url
eg: // define relationships - focus on "source" and "target" // "source_type" and "target_type" is extra data used to selectively truncate data set var _data = [ {"source": "Account", "target_type": "Master", "target": "Cost Center", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "GL Entry", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "Journal Voucher", "source_type": "Master"}, {"source": "Account", "target_type": "Master", "target": "Mode of Payment", "source_type": "Master"},
Is there a data dictionary in the database somewhere that describes the relationships between database tables and describing relation type eg: 1 to many; many to many etc...
In addition are there any diagrams showing the tables layed out using a err diagramming tool like "mysql-workbench"
I would like to contribute to the project some of the systems we have developed for our internal accounting over the years and teh ER Diagram is absolutely necessary to be an effective contributor.
If the database tables are created by the Doc Types definition then where are the doc type definitions stored? In the database? Where exactly are the primary key and foreign keys defined for each doc/table?
Why do some tables not have a primary key of a unique “id” but appear to use the name/description as the key to join to other tables eg contact.name etc… This seems to create a problem with updating the name and having to deal with cascading updates to other tables violating basic database normalization standards.
Have I missed something basic here?
On Thursday, May 9, 2013 12:53:21 PM UTC+10, rushabh wrote:
Erran,
The table relationships are exactly same as DocTypes. Every time a DocType is saved, the schema is updated. You can get a better idea by browsing DocTypes. If you are logged in as Administrator, go to #List/DocType in the url
eg: // define relationships - focus on "source" and "target" // "source_type" and "target_type" is extra data used to selectively truncate data set var _data = [ {"source": "Account", "target_type": "Master", "target": "Cost Center", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "GL Entry", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "Journal Voucher", "source_type": "Master"}, {"source": "Account", "target_type": "Master", "target": "Mode of Payment", "source_type": "Master"},
Is there a data dictionary in the database somewhere that describes the relationships between database tables and describing relation type eg: 1 to many; many to many etc...
In addition are there any diagrams showing the tables layed out using a err diagramming tool like "mysql-workbench"
I would like to contribute to the project some of the systems we have developed for our internal accounting over the years and teh ER Diagram is absolutely necessary to be an effective contributor.
On Sat, May 11, 2013 at 3:52 PM, Erran Botha <er...@gmail.com> wrote:
Thanks Rushabh,
That worked.
If the database tables are created by the Doc Types definition then where are the doc type definitions stored? In the database?
In ".txt" files -- for example app/accounts/doctype/account/account.txt - whenever you update the system using "lib/wnf.py --update" all schema is automatically updated
Where exactly are the primary key and foreign keys defined for each doc/table?
"Link" fields are foreign keys.
Why do some tables not have a primary key of a unique "id" but appear to use the name/description as the key to join to other tables eg contact.name etc..
All tables have a unique "name" (which is actually id). This could be a numeric series or name (based on user preferences in masters like Customer, Supplier, Item)
This seems to create a problem with updating the name and having to deal with cascading updates to other tables violating basic database normalization standards.
We have a slightly custom designs for this. For cascading updates, you have to use the API - all the triggers are written in Python files in the DocType folders (see the account folder)
Have I missed something basic here?
On Thursday, May 9, 2013 12:53:21 PM UTC+10, rushabh wrote:
Erran,
The table relationships are exactly same as DocTypes. Every time a DocType is saved, the schema is updated. You can get a better idea by browsing DocTypes. If you are logged in as Administrator, go to #List/DocType in the url
eg: // define relationships - focus on "source" and "target" // "source_type" and "target_type" is extra data used to selectively
truncate data set var _data = [ {"source": "Account", "target_type": "Master", "target": "Cost Center", "source_type": "Master"},
{"source": "Account", "target_type": null, "target": "GL Entry", "source_type": "Master"}, {"source": "Account", "target_type": null, "target": "Journal
Voucher", "source_type": "Master"}, {"source": "Account", "target_type": "Master", "target": "Mode of Payment", "source_type": "Master"},
Is there a data dictionary in the database somewhere that describes the relationships between database tables and describing relation type eg: 1 to many; many to many etc...
In addition are there any diagrams showing the tables layed out using
a err diagramming tool like "mysql-workbench"
I would like to contribute to the project some of the systems we have developed for our internal accounting over the years and teh ER Diagram is absolutely necessary to be an effective contributor.