I am having a weird issue with alloy model generating an unescaped query, even though it uses prepared statement.
To recreate it:
1. Create a model with a non integer primary key.
2. Do a simple model.fetch({id: "your_text_id"});
It will generate a query like so: SELECT * FROM table_name WHERE some_primary_key = your_text_id
where you would expect something like the following: SELECT * FROM table_name WHERE some_primary_key = 'your_text_id'
quoted from:
http://developer.appcelerator.com/question/162301/weird-sqlite-escaping-issue
Moving this ticket to engineering based on Tony's comment in the Q&A thread included in this ticket.
Tested using attached sample app on Alloy 1.3.0 and 1.4.1. Can't reproduce the issue on v1.4.1.
config: { columns: { "name": "TEXT", "countryId": "TEXT PRIMARY KEY" }, adapter: { type: "sql", collection_name: "countries", idAttribute: "countryId" } },model.fetch({id:'SIN'});Marking as failed because there doesn't seem to be a way to cancel a review.
We are not able to reproduce the issue. Perhaps an intervening change since 1.3.0 has resolved this issue. Please comment here if this remains an issue for you. If you do so, please make sure there's a sample app attached that demonstrates the problem.