|
From: Krzysztof <k.k...@gm...> - 2007-10-16 22:58:27
|
In my oppinion such solution is an overkill, that doesn't buy much in the long run. Database would be justified if there would be the need for at least parts of ACID. Neither there is a lot of data, nor efficiency and optimisations matter. And for the sake of Consistency alone it's not really worth it, I guess. One advantage (especially with sqlite3) is that one don't have to mess with files, formats, records etc. But now one has to mess with SQL! Altering table schema now breaks code in various places (exactly like in current implementation, less so in OO version). Another thing is that database like sqlite doesn't really give enough flexibility with regard to data types and expressiveness. So data marshalling comes to play, and in (near or far) future massaging game objects into rows and tables and vice-versa. Of course it can be done, but thats another layer of glue that somebody would have to write. Scripting SQL backend would be supposedly easier, but only because of common interface (that is standarised and already implemented - thats the plus). Except for that - it's exactly the same like in any other scenario. As much as I don't like XML, I'd rather go for XML than SQL :) But If you want to experiment that's something worthwile. I'd love to see a resutl showing that it is a good idea... Just my 2 cents, -- Krzysztof Kościuszkiewicz Skype: dr.vee, Gadu: 111851, Jabber: ko...@ja... Mobile IRL: +353851383329, Mobile PL: +48783303040 "Simplicity is the ultimate sophistication" -- Leonardo da Vinci |