What database are we going to use ?

Content and general development discussion, including maps, quests, and server code from the development team.
Post Reply
User avatar
Usiu
Peon
Peon
Posts: 15
Joined: 06 Mar 2005, 19:39
Location: Poland
Contact:

What database are we going to use ?

Post by Usiu » 08 May 2005, 07:21

I suggest Postgresql

* Its easy to configure
* Stable, popular and powerful
* Good documentation
* libpq can be compiled on windows (http://www.sql.org/sql-database/postgre ... win32.html)

Any other suggestions ?
User avatar
gene
Peon
Peon
Posts: 28
Joined: 10 Aug 2004, 19:35

Post by gene » 08 May 2005, 07:39

PostgreSQL is under the GPL.
MySQL is under the BSD license.

Here's a nice comparison of the two: http://www.devx.com/dbzone/Article/20743

I'm a fan of MySQL, but that's only personal preference. I've yet to use postgre, so I can't speak on technical differences myself.

I do love that BSD license, though.
User avatar
nym
Novice
Novice
Posts: 116
Joined: 18 Aug 2004, 11:01
Contact:

Post by nym » 08 May 2005, 10:30

I think SQLite will be put in use immediately, while other DBMS bindings would come later. As SQLite is: a) fast. b) small

When it comes to DBMS, i would use PostgreSQL over MySQL anyday. Especially when PostgreSQL is the most standard compliant SQL available (Postgre is on its way to SQL:2003 compliance, and MySQL misses out _alot_). But when it comes to performance, MySQL wins hands down against PostgreSQL (as most cut down software does). When it comes to licensing, i think PostgreSQL is the better of the two (as BSD can be proprietorized).

Wow.. 110010 posts..
YOU ARE READING THIS!
User avatar
Usiu
Peon
Peon
Posts: 15
Joined: 06 Mar 2005, 19:39
Location: Poland
Contact:

Post by Usiu » 08 May 2005, 11:28

So we need a c++ wrapper for sqlite3
added wrapper by Ren? Nyffenegger.

So the thread is closed :)
User avatar
gene
Peon
Peon
Posts: 28
Joined: 10 Aug 2004, 19:35

Post by gene » 08 May 2005, 18:31

What are you intending on using the database for, client or server?

If the source for the database software isn't modified, licensing doesn't matter (except that it's free).
User avatar
Bjørn
TMW Adviser
TMW Adviser
Posts: 1430
Joined: 09 Dec 2004, 19:50
Location: North Rhine-Westphalia, Germany
Contact:

Post by Bjørn » 08 May 2005, 21:37

Only the server will store persistent dynamic data in a database, it doesn't concern the client which doesn't need to remember dynamic data across sessions.
User avatar
clsdaniel
Peon
Peon
Posts: 4
Joined: 06 Jul 2005, 06:40

Database Backend

Post by clsdaniel » 06 Jul 2005, 06:46

You could look the the ODK project, which offers a database agnostic access, and has C++ bindings, works on Linux, *BSD and Windows, and currently supports SQLite, MySQL and PostgreSQL, SQLite3 plugin is on development and will support other databases as well, transparently.

Ok, that was a shameless plug, but there is the advantage that i'm the developer ;), and can help providing any feature and coding for the project.

Site: http://odkit.sourceforge.net
E-Mail: clsdaniel@gmail.com
User avatar
ElvenProgrammer
TMW Adviser
TMW Adviser
Posts: 2526
Joined: 13 Apr 2004, 20:11
Location: Italy
Contact:

Post by ElvenProgrammer » 06 Jul 2005, 09:00

Oh I thought it was already supporting SQLite3. We're "using" it, so I guess the first thing to do would be add support for it, if we decide to use odk.
User avatar
Verious
Peon
Peon
Posts: 42
Joined: 23 Apr 2005, 20:31
Location: Online
Contact:

Post by Verious » 06 Jul 2005, 14:38

I would suggest only selecting from database applications that support stored procedures and triggers as these can greatly increase performance (especially if the database is moved to a different machine than the server), improve security, and significantly improve data integrity and consistency.
User avatar
nym
Novice
Novice
Posts: 116
Joined: 18 Aug 2004, 11:01
Contact:

Post by nym » 07 Jul 2005, 03:06

Eh? I wouldn't really worry: there is a generic database interface which kindjal has written, which currently has backends for MySQL, PostgreSQL and SQLite3. Support for more databases will be added later if needed.
YOU ARE READING THIS!
Post Reply