AIR Tip 12 – Working with the SQLite Database

Posted by David Tucker in AIRApr 18th, 2008 | 4 responses

The SQLite database inside of AIR provides a great deal of functionality that can be used to create a great many different types of applications. In this article, I have placed links to the tutorials I have been writing over at InsideRIA.com on how to use this functionality (I am about halfway through this series). Let me know if you have any questions – and I can address them in the upcoming tutorials. Currently, I have covered topics such as: connecting to a database, running basic queries, strongly typing query results, and parameterized queries.

My SQLite Tutorials at InsideRIA.com




4 Responses to “AIR Tip 12 – Working with the SQLite Database”

  1. vkminds says:
    April 21, 2008 at 9:30 am

    hi,

    just wondering if it is possible to import a CSV file into AIR and synch it to the SQLite database?

  2. David Tucker says:
    April 21, 2008 at 9:40 am

    You could actually do this in AIR (and have it look over the CSV file), but in most cases, you will want to use one of the SQLite administration tools to create the database, and then you can just include it in your AIR application (that is what I did for the tutorials at InsideRIA).

    I put a list of SQLite administration resources on InsideRIA at the end of this article:

    http://www.insideria.com/2008/03/air-api-introduction-to-the-sq.html

  3. Ben says:
    December 16, 2008 at 5:08 am

    Strong typing is giving me a fit with AIR’s flavor of SQLite.

    How can you create insert statements using sqlStatement.parameters[@x] and avoid type mismatch errors when inserting values into an integer data type ?

  4. Ganesh says:
    September 25, 2009 at 3:23 am

    Hi,

    My AIR application has SQLite DB with more than 100K rows and i have 5 components in the UI providing various visualization of the data, which includes data, image, 3 charts and summary section.

    When the data volume goes up the querying and filtering of the records is taking more time, i.e., refreshing components.

    Did the following.

    - Optimized all the query and also made all DB calls (only select) asynchronous, this gave some improvement
    - Query time is very low now even for table with more than 100K records, the issue is rendering of the components. Any specific things you can think of suggesting.

Leave a Reply