1,605
edits
Changes
From Gramps
no edit summary
Is your most current work on the schema at [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/plugins/export/ExportSql.py?view=markup trunk/src/plugins/export/ExportSql.py]? I'd prefer to keep our work coordinated together. We could just work directly with the exportsql.py module but it may make sense to work with more of a straight up db import file of just table creates and drops. relationships could be put in comments. that might make it less clutter for the main devs when we pitch it to them. Another option would be to create an actual table chart. have you ever used dia? I haven't found a really great table charting app yet but dia does an OK job. I don't have svn commit yet. how would you prefer to pass work back and forth? a tracker item. wiki page or wiki media file? Also to recap should we just use the exportsql.py code, db import file, or table mapping chart? --[[User:AaronS|AaronS]] 04:35, 30 March 2009 (UTC)
Yes, that is the first stab at just creating a simple sqlite export... mostly just thinking out loud there. I agree that it would be a good idea to diagram the tables. It would be nice to have a table representation that could '''generate''' UML, dia, code... perhaps all we need to do is describe the tables in a text file, which could be read in by our programs to generate these outputs? I guess the XML doesn't work for that role, as it is hierarchical ... maybe a flat XML DTD version? --[[User:Dsblank|Dsblank]] 14:50, 30 March 2009 (UTC)
