Database handling internal to Procon about potato

[m4cx]

According to these requirements, I think we should implement a whole storage abstraction layer.

So the admin can decide weather to store data in mysql, nosql, filesystem, sql, oracle or whatever.

We should also think about migration paths, changes to a data model and so on.

[phogue]

Migration handling will be included, but will need to be initiated by a plugin to ensure its tables are updated. Procon will setup a migration collection itself when a database is opened, but otherwise all alterations will be passed from the plugin like other queries.

Migration will support version, up() and down(). Probably indexed by the plugin Guid. More than likely a bunch of other meta data for kicks.

Collections, via standardized naming convention, will be restricted to a plugin, a plugin on a specific connection or global to all connections/plugins.

I'm not busting a gut on other storage options beyond MySql, MongoDb and SqlLite. I've had a couple people ask for MsSql about a year ago, otherwise most hosts just run MySql. I'm the one pushing Mongo on people cause I think it's neat :)

Procon itself only requires a migration model, otherwise it shouldn't know of anything in the database. With this in mind something can easily be thrown together, much like a plugin would. The entire database support is simply so plugins have something to use and we can lock the the plugin appdomain security down a little bit.

Results of queries will more than likely be passed back to the plugin/daemon client in json. Allows for queries to be initiated over the daemon with results. Since we're using the Newtonsoft.Json plugin developers will be able to easily deserialize this back to an array of a certain type of object.

[phogue]

This branch has been merged in. Procon.Database and Procon.Database.Serialization are functionally complete. Refactoring and changes will undoubtedly occur.

I need this in the main branch to begin adding functionality to Procon.Core.Database namespace so plugin unit testing of database functionality can begin easily.