FEATURE: MapTool Database

[JamzTheMan]

Um ya, lets start with just simple select and update SQL calls for now.

I say we put out a simple DB like derby with some simple functions and put that in a version and see what the user base does with it. Give em some import/export commands as well. I can't see MT really needing anything too crazy/complicated here. We don't need Big Data or anything.

[RPTroll]

Is the thought to provide convenience functions or make folks learn sql?

Initial implementation just sql?

[JamzTheMan]

First thought is to just pass SQL but... then we don't know what the users are passing?

Then do we have to parse the SQL to allow/abort anything we do/don't want?

May need a single function, first param being select/update/create/drop (probably more) with 2nd parameter being the criteria?

Dunno, I know enough SQL to be dangerous but will bow to Craig or other DB gods on what could/couldn't get us into trouble. Hate to have to write a SQL parser but obviously we have to apply some restrictions.

[RPTroll]

For tables I would say use a grid editor to start. I'm sure there's one out there that will load, track changes, and save to a database.

Here's one http://quicktablejava.appspot.com/

Implement then dismount. Take a victory lap. Call it done until the next level of functionality.

[JamzTheMan]

True, probably a lot of open source plugins we could use. Someone do a POC.

[RPTroll]

Step 0: Determine DB and implementation strategy.

We have Derby proposed (java built in).

Other candidates?

[aliasmask]

How about H2 following mote's lead. Here's their comparison guide:

http://www.h2database.com/html/features.html#comparison

[RPTroll]

Here's another link with a bit more text and not associated with a product.

text.http://lightjavadatabase.blogspot.com/2 ... abase.html