High Level Database Access: Difference between revisions

Content deleted Content added

Revision as of 10:56, 1 March 2010 view source imported>Hendrik Brummermann No edit summary ← Older edit		Latest revision as of 23:25, 18 September 2010 view source imported>Hendrik Brummermann No edit summary
(25 intermediate revisions by the same user not shown)
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://~~stendhal.game-host~~stendhalgame.org/hudson/job/marauroa_HEAD/javadoc/marauroa/server/game/db/package-summary.html DAO package]. Note that games can add their own DAOs. So lets assume you want to log a gameEvent about a player logging out: 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 46: Please note that commit() will automatically perform a rollback and throw an SQLException if there have been any errors. {{#breadcrumbs: [[Marauroa]] \| [[Navigation for Marauroa Users\|Using]] \| [[High Level Database Access]] }}