Maybe we could keep the data in some plain text format and then just have scripts that can weave it into the different formats as required? This might be easiest for ensuring that there is only ever one primary source and different versions don't have to be maintained?
-Dan On Mon, May 19, 2008 at 9:15 PM, David Primmer <[EMAIL PROTECTED]> wrote: > I have some updated data people, social graph, activities, that I'd > like to add to shindig but I'm wondering the best way to store it and > work with it. Anyone have a suggestion? I'd like to replace the > state-basicfriendlist.xml file with something that's easier to edit > and work with that could be checked into shindig. Some suggestions > from the summit were http://www.hsqldb.org/, > http://db.apache.org/derby/ and http://www.sqlite.org/, the latter > being c-based. > > I'm primarily interested in supporting the java rest api so hsqldb > sounds best but I'm sure the other implementations would like to use > the same source data and may want something with more runtime > availability. Maybe we could store the seed data in multiple formats > for seeding a few different small database engines but we should start > with one. > > I'd like to avoid non-embeded stuff like MySql. > > There's been a request not to have the database engine included in the > shindig jar. We'd have to design the maven rules to generate alternate > binaries. Here's the maven rule to add hsqldb: > > <dependency> > <groupId>hsqldb</groupId> > <artifactId>hsqldb</artifactId> > <version>1.8.0.7</version> > <scope>test</scope> > </dependency> > > davep >
