Thanks Eric,
All of your work effort for Flex / AIR community is amazing. Thanks for posting this one up.

Cheers,
W.

Well I figured out myself. I’m just using 1 SQLService and for the rest some delegates.

I dived a little bit into the code and have some questions.

In SQLStatementHelper you are using StringUtil.substitute to create the sql statement. I don’t think this safe related to SQL injection. Shouldn’t you use ? or named parameters instead?

I also noticed that in the execute method the itemClass is only set when it provided (not null). In case statements are reused (and this is the case for the sych executed method!!) then it could happen that a previously set itemClass is used in the query. I don’t know if this could cause any problem, but why not set always the itemClass?

Cheers,
Marcel

I get the following error:

Unable to resolve resource bundle “queries” for locale “en_US”.

How to fix this.

Thanks

M

how to use “create table” to define fields type and fields in air caingorm?

Thanks

M

Ah, I found the event dispatcher in SelectUsersCommand.as. I thought it was being manually dispatched, I ran profiling on it to see what classes were being called during spin up and saw SelectUsersCommand in the list which led me to it.
Thanks for the lib!

Hi, first thanks very much for your air-cairngorm, I’m a big fan of cairngorm and I use it for my every project cause of it simplicity and ability to extend.
I’m playing with air-cairngorm now and I had some difficulties when mapping data types to SQL cause there are affiliates in air SQLite. I got problems with it, especially with DATE class.
I modified it a bit to get rid of the string and now in SQLService I simply pass the SQLStatement instead of string so I get rid of the string class and also the speed is better with large statements.
I now pass the parameters ex.
SQL statement: INSERT_USER = INSERT INTO users (username, password, some_date, todo) VALUES( :username, :password, :some_date, :todo)

and sample function in the delegate now looks like this

public function addUser(user:UserVO) : void
{
var statement:SQLStatement = new SQLStatement();

statement.text = SQLStatementConfiguration.INSERT_USER;
statement.parameters[‘:username’] = user.username;
statement.parameters[‘:password’] = user.password;
statement.parameters[‘:some_date’]= user.date;
statement.parameters[‘:todo’] = user.todo;

sql.openConnection(statement, responder, UserVO);
}

where UserVO is simply class with

public var username:String;
public var password:String;
public var date:Date;
public var todo:Boolean;

I hope that it makes sense.
Maby you got better idea how to map the objects to the table.
Thanks.

Hey Vane, nice comment, I too had the same problems with errors in the string being passed in Eric’s class for sqlstatement. I simply extended the appropriate class like this and now I pass the sqlstatement object, it works a treat, thx for your work Eric:

package com.wmanager.control.other.customClasses
{
import com.ericfeminella.air.cairngorm.business.ISQLResponder;
import com.ericfeminella.air.cairngorm.business.SQLService;

import flash.data.SQLStatement;
import flash.net.Responder;

public class SQLStatementService extends SQLService
{
public function SQLStatementService()
{
super();
}
public function executeStatementAsync(statement:SQLStatement, responder:ISQLResponder, dataType:Class = null, prefetch:int = -1.0) : void
{
_statement = statement;
_statement.sqlConnection = _connection;
//_statement.text = statement;

if ( dataType != null )
{
_statement.itemClass = dataType;
}

_statement.execute( prefetch, new Responder( responder.result, responder.fault) );
}

}
}

Hi Eric,
great component!
One question, have you thought about a switch or something for encrypted local databases? As I’m currently implementing such a thing using your component, would the code be of interest to you?

regards Jonas

Hey Eric,
nice to hear that!
I extended your SQLService class to work with encrypted databases, worked like a charm due to the ease in extending it.
One more question though, as I read both vane and mikeydevs comment on problems with the string statements, especially in the case of vane problems with Date-objects. Is there a problem saving Date-objects with your current implementation, and is their way the way to go (as I understand them, they just removed the String-statements entirely)?
I’m asking because right now I’m facing problems with Date-objects, too. It seems the Date is converted to a String before passing it into the statement itself, and thus is no longer recognized as a Date when trying to execute the statement, resulting in a “could not convert string value to date” SQLError (Error #3132: Data type mismatch.).

regards Jonas