MantisBT - Zandronum
View Issue Details
0000204Zandronum[All Projects] Suggestionpublic2010-11-21 23:102018-09-30 21:36
Galaxy_Stranger 
 
normalfeatureN/A
closedfixed 
MicrosoftWindowsXP/Vista/7
98d 
1.3 
0000204: In-game Database Interface
It would be great to have an interface to some sort of database, whether it was an external MySQL or local SQLite database.

Then, persistent storage can be saved for individual players - like inventory and stats. Game logic can also be influenced by database values.
ACS, DECORATE and the console could access the database. User authentication could also be implemented via the database.
No tags attached.
related to 0001176new  Account system development/discussion 
Issue History
2010-11-21 23:10Galaxy_StrangerNew Issue
2010-12-10 22:27TIHanNote Added: 0000719
2010-12-12 00:58Galaxy_StrangerNote Added: 0000726
2014-06-07 20:52WatermelonRelationship addedrelated to 0001176
2014-06-07 20:53WatermelonStatusnew => closed
2014-06-07 20:53WatermelonResolutionopen => duplicate
2014-06-07 20:53WatermelonFixed in Version => 2.0
2014-06-07 21:42WatermelonStatusclosed => resolved
2014-06-07 21:42WatermelonResolutionduplicate => fixed
2014-06-07 21:42WatermelonFixed in Version2.0 => 1.3
2018-09-30 21:36Blzut3Statusresolved => closed

Notes
(0000719)
TIHan   
2010-12-10 22:27   
I have thought about actually putting in MySQL or SQLite in Skulltag for a long time now and making them accessible by ACS. MySQL and SQLite gives you the connector C++ code so you can access the database. The problem is that this connector code provided by MySQL and SQLite is GPL; therefore, it violates the license of Skulltag in a lot of ways.

Perhaps there could be another way Skulltag can access a SQL database. I do agree to this suggestion 100%, but the problem is licensing.
(0000726)
Galaxy_Stranger   
2010-12-12 00:58   
The license shouldn't affect anything?

The GPL would only affect the project if you were modifying the MySQL database server and redistributing it. All you would be doing is writing an interface to the database which uses the MySQL interface. You're not even redistributing the freely available database software, and you're not integrating the MySQL server software into the Skulltag project.

It's the same as using MySQL for a web site - you aren't required to release your source just because you connect to the database.

And the more I think about it - MySQL would be preferable to SQLite in that separating the database from Skulltag would make it platform independent - and I would think you wouldn't necessarily have to make code-specific changes to the Linux version. Maybe you would...

Anyway, I wouldn't think that the GPL would be an issue. But there's always PostgreSQL: 'http://www.opensource.org/licenses/postgresql [^]'