Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tree: 9abae95a25
Fetching contributors…

Cannot retrieve contributors at this time

90 lines (63 sloc) 2.744 kb

persistence.backend.mysql.md

This library implements some wrappers to let persistence.js work with a MySQL database in a node.js environment. Although not fully stable it is usable at this point using nodejs-mysql-native library (which you have to download and include in your project manually).

Use of persistence.js is slightly modified to deal with multiple concurrent session in the node.js application. A Session object needs to be passed as an extra argument to certain method calls, typically as a last argument. Methods usually called on the persistence object itself are now called on the Session object.

An example node.js application is included in test/node-blog.js.

Setup

You need to require two modules, the persistence.js library itself and the MySQL backend module:

var persistence = require('./persistence').persistence;
var persistenceBackend = require('./persistence.backend.mysql');

Then, you configure the database settings to use:

persistenceBackend.configure('database', 'username', 'password');

Subsequently, for every connection you handle (assuming you're building a sever), you call the persistenceBackend.getSession() method:

var session = persistenceBackend.getSession();

This session is what you pass around, typically together with a transaction object. Note that currently you can only have one transaction open per session and transactions cannot be nested.

session.transaction(function(tx) {
  ...
});

Defining your data model

Defining your data model is done in exactly the same way as regular persistence.js:

var Task = persistence.define('Task', {
  name: "TEXT",
  description: "TEXT",
  done: "BOOL"
});

A schemaSync is typically performed as follows:

session.schemaSync(tx, function() {
  ...
});

Creating and manipulating objects

Creating and manipulating objects is done much the same way as with regular persistence.js, except that in the entity's constructor you need to reference the Session again:

var t = new Task({}, session);
...
session.add(t);

session.flush(tx, function() {
  ...
});

Query collections

Query collections work the same way as in regular persistence.js with the exception of the Entity.all() method that now also requires a Session to be passed to it:

Task.all(session).filter('done', '=', true).list(tx, function(tasks) {
  ...
});

Closing the session

After usage, you need to close your session:

session.close();
Jump to Line
Something went wrong with that request. Please try again.