Comments on: Storing an ActionScript Object class in SQLite with AIR

By: Neil

Neil — Thu, 16 Sep 2010 08:22:07 +0000

Thanks for sharing this info, just wondering why do you extend Object? I thought every class eventually extends Object in Actionscript.

By: Sam

Sam — Mon, 05 Jul 2010 10:44:26 +0000

Thanks for the heads-up on itemClass Abhishek
That looks good but you need to have a table for each class, I’m sure ill find more of a use for this one over registerClassAlias.

By: Abhishek

Abhishek — Sun, 04 Jul 2010 19:40:05 +0000

Sam, have you tried using the itemClass property of a SQLStatement? That does most of the work for you.

http://help.adobe.com/en_US/AS3LCR/Flash_10.0/flash/data/SQLStatement.html#itemClass

By: Sharedtut

Sharedtut — Wed, 03 Feb 2010 14:20:57 +0000

Great job, thank you for sharing.

By: Sam Hassan

Sam Hassan — Fri, 22 Jan 2010 11:22:26 +0000

Thanks Andrew,

This is just a little example and not how I usually code, normally I would have a Database controller handling the setup and another class or several classes dealing with the service methods.

I’m always appreciative of your knowledge
I like this letter: http://writing.bryanwoods4e.com/

By: Andrew

Andrew — Thu, 21 Jan 2010 10:34:55 +0000

Good post.
A pattern that follows from this is the Repository pattern.. as your application grows your Controller class is in danger of overgrowing with data storage logic, so a way to separate this out would be to create a DaveRepository class, as in:

public class DaveRepository extends Object
{
private var _database : SQLConnection;
public function DaveRepository(Database : SQLConnection) : void {
registerClassAlias(“DataVO”, DataVO);
this._database = Database;
}

public function Add(daveVO : DaveVO) {
// … database logic here
}

public function All() {
…
}

.. etc
}

Then your controller just looks like this:

public class Controller extends MovieClip
{
private var theDB : SQLConnection
public function Controller()
{
theDB = new SQLConnection(); // etc etc
}

public function SaveDave()
{
DaveVO dave = new DaveVO();
dave.name = “dave”;
dave.number = randRange(0,100);

new DaveRepository(theDB).Add(dave);
}
}

Makes your controller much lighter. Pays to move all your DB connection logic into a single class too and have all your repository classes accept a DB connection class in the constructor.