Difference between revisions of "User talk:Dsblank"

From Gramps
Jump to: navigation, search
Line 2: Line 2:
  
 
Thanks for everything. I appreciate all your work with GRAMPS very much. That should be obvious anyway: who wouldn't? --[[User:Lcc|Lcc]] 19:46, 22 March 2009 (UTC)
 
Thanks for everything. I appreciate all your work with GRAMPS very much. That should be obvious anyway: who wouldn't? --[[User:Lcc|Lcc]] 19:46, 22 March 2009 (UTC)
 +
 +
== DB Schema ==
  
 
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. --[[User:AaronS|AaronS]] 04:37, 29 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. --[[User:AaronS|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 [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/data/grampsxml.dtd?view=markup 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!  --[[User:Dsblank|Dsblank]] 23:19, 29 March 2009 (UTC)
 
If you wanted to help explore the DB schema, you could attempt to derive a set of tables from the [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/data/grampsxml.dtd?view=markup 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!  --[[User:Dsblank|Dsblank]] 23:19, 29 March 2009 (UTC)
 +
 +
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)

Revision as of 04:35, 30 March 2009

Hello Doug,

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)

DB Schema

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)