Comments for The AngrySprite

Comment on ActionScript SQLite ORM by Arnaud PEZEL

Arnaud PEZEL — Thu, 06 Nov 2008 18:39:36 +0000

Hi,

I recently started an Air ORM for a project. It will be released open source quickly. It’s named SOFA. You can check avilability on http://www.matsiya-technology.com (my company blog), there’s a post about it.

Comment on Simple ActionScript ORM example by Camlin

Camlin — Wed, 29 Oct 2008 03:18:13 +0000

Thanks for writing this.

Comment on ORM project delay by ffxmwcnp

ffxmwcnp — Wed, 13 Aug 2008 00:49:12 +0000

ffxmwcnp…

ffxmwcnp…

Comment on ORM project delay by Gareth

Gareth — Thu, 15 May 2008 14:33:02 +0000

I look forward to it

Comment on Simple ActionScript ORM example by Gareth

Gareth — Tue, 13 May 2008 17:37:52 +0000

Just checking in to see how the code has been going lately. I’ve created a new AIR app and am anxious to try out your latest code (and see if I can offer any assistance) so I thought I’d chime in and bug you again But if I can help out, just let me know (not sure what I’d be able to do exactly, but…)

Comment on Simple ActionScript ORM example by reallypride

reallypride — Mon, 28 Apr 2008 13:48:57 +0000

Very good,expecting it.

Comment on Dynamic SQL querys in ActionScript by Matthew

Matthew — Tue, 22 Apr 2008 21:21:38 +0000

Thank you for the feedback.
I agree that passing the objects/arrays in is not very elegant. I went with that for the now because this allow for me to move forward with my testing and get the big picture working.

This is very much a work in progress.

Comment on Dynamic SQL querys in ActionScript by Gareth

Gareth — Fri, 18 Apr 2008 16:07:07 +0000

I really like what you’ve done so far. It would certainly make the SQL creation much easier. The Adobe application, Employee Directory, (I think) uses the Cairngorm model and moves all of the SQL calls into separate AS classes. These are then passed to a SQLmanager which invokes the necessary SQL call, and passes the results back to the calling page. This somewhat separates the SQL code from the AS code, but requires one page for each SQL statement, which can get a little overwhelming if you have many calls to the SQLite dB.

The only thing that I did not like *too* much is passing in the objects into the filter array. It’s all a little mysterious as to what to pass in to the array. A new user would not know exactly what to pass in without either the code or an API.

Here’s something that I’m not sure would work completely, but might or might be a step in the right direction

How about creating a FilterableObject? This object would have public methods for each of the properties within your case statements in your parseTerms method. Each of the methods would return “this” (the FilterableObject), so you could do
new FilterableObject().isNotNull( ‘insider_id’ ).iExact( ‘name’, ‘adsf’ ) etc., and chain everything together. Eclipse would then be able to generate the “hints” as you’re typing and the array that is passed in wouldn’t be as mysterious to a new user.

Anyway, this will be a really useful piece of code once it’s finished, and I look forward to seeing it completed.