High Level Database Access: Difference between revisions
Content deleted Content added
imported>Hendrik Brummermann |
imported>Hendrik Brummermann No edit summary |
||
| (68 intermediate revisions by 2 users not shown) | |||
Line 1:
{{Navigation for Marauroa Top|Using}}
{{Navigation for Marauroa Users}}
Line 7:
This article describes how you can use Marauroa in your games to
Most of the database access is transparent. For example if client requests the creation of an account and the game server logic accepts that request, Marauroa will automatically add the necessary rows to the database.
Line 15:
== Data Access Objects ==
In compliance to the Marauroa architecture, database access related code is not spread all over the code base but concentrated in a set of data access objects (DAO). There is JavaDoc available for the complete [http://
So lets assume you want to log a gameEvent about a player logging out:
Line 29:
</source>
Now games can register their own subclass
== Transactions ==
Line 38:
DBTransaction transaction = TransactionPool.get().beginWork();
try {
DAORegister.get().get(GameEventDAO.class).addGameEvent(transaction, playerName, "saved");
DAORegister.get().get(GameEventDAO.class).addGameEvent(transaction, playerName, "logout");
} finally {
TransactionPool.get().commit(transaction);
Line 45:
</source>
Please note that commit() will automatically perform a rollback and throw an SQLException if there
{{#breadcrumbs: [[Marauroa]] | [[Navigation for Marauroa Users|Using]] | [[High Level Database Access]] }}
| |||