Thanks for everything. I appreciate all your work with GRAMPS very much. That should be obvious anyway: who wouldn't? --Lcc 19:46, 22 March 2009 (UTC)
How goes the work on the DB schema? Could I help? I think I've done all the research on DB abstraction that I can. I'm not certain it's necessary to push the main devs on an abstraction layer quite yet. I'd like to test them out a little first. The DB schema is something we can nail down and push for a consensus on though. --AaronS 04:37, 29 March 2009 (UTC)
If you wanted to help explore the DB schema, you could attempt to derive a set of tables from the GRAMPS XML dtd. This is a different approach from what I was doing (converting the Python BSDDB code directly to DB schema, keeping intact all GRAMPS handles, and making up new ones where required). Thanks for getting this ball rolling! --Dsblank 23:19, 29 March 2009 (UTC)
Is your most current work on the schema at 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? --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? --Dsblank 14:50, 30 March 2009 (UTC)
Do you have a specific solution in mind? That would be nice but I haven't heard of anything that can do all that. I was thinking the easiest would be to just have a import.sql file that would have all the sql to create the tables. We might have to have some additional notes but there aren't too many tables so a full table mapping chart might not be necessary though nice. Most 3rd party sqlite db tools should be able to just automatically load them and export them. firefox has a sqlite manager plugin that I've used in the past. https://addons.mozilla.org/en-US/firefox/addon/5817. I know we haven't fully settled on sqlite but it should be fine for a schema mockup. --AaronS 17:36, 30 March 2009 (UTC)
I don't have time right now to start looking into them but there may be some options that might help with at least some of it. Unless you have a specific solution in mind i'll do some research on them later.
- http://tedia2sql.tigris.org/ (i know dia is cross platform so i'll check this out first) but I don't think it has sqlite support but for schema mysql queries should look close enough for discussion.
--AaronS 18:23, 30 March 2009 (UTC)