Julien Bayle

I'm using a sqlite that works very fine in the max editor.

I built an application for standalone purpose.

I'm sure the standalone application opens the database and the path are correct.

But when I execute a select, it always return none results :-(

I verified, in the support folder I have the extensions/sqlite.mxe etc.

I'm stuck and it stucks 70% of my systems in the exhibition :-(

any tips, helps, path would be very appreciate and if it could be relatively fast, I'd pay you a soda :)

I built an application for standalone purpose.
I'm sure the standalone application opens the database and the path are correct.
But when I execute a select, it always return none results :-(

any one here?
I'm stuck and it stucks 70% of my systems in the exhibition :-(

any tips, helps, path would be very appreciate and if it could be relatively fast, I'd pay you a soda :)


sqlite-works-fine-but-doesnt-work-on-my-standalone

after have troubleshooted A LOT today, I can almost write: there is a bug.

- the database is opened (it complains if it wouldn't be)

did someone use it in a standalone mode ?

I'm on windows 7 64bits. now, all my other patches work fine, this is the LAST part that sticks me !

I'll make a workaround (txt files, parsed, stored in a JS array etc)

after have troubleshooted A LOT today, I can almost write: there is a bug.
the most amazing thing is: no complaint.
- the database is opened (it complains if it wouldn't be)

did someone use it in a standalone mode ?
I'm very curious.
I'm on windows 7 64bits. now, all my other patches work fine, this is the LAST part that sticks me !

I'll make a workaround (txt files, parsed, stored in a JS array etc)


As I recall (I am at day job and free doc access is far away)

To have "persistence" with SqlLite, you need to declare a filename to persist to : a flat file version of all the SQLLite db objects. Without this, all sqlLite work is "ephemeral": it goes away when you free the sqlLite object.

SO... by extension, if you wish to have a persisted set of data ina standalone, that is there every time the standalone is started, you will have to have the SQLLite db written down as a file somewhere, and tell SQLLite to load said DB file on startup: all this I saw long ago,in a intro to SQLLite or somesuch, so use a grain of salt here, and look it up yourself....

Think about it: where are those table definitions and rows of data gonna be stored in your standalone? Init into and persist from the SQLLite DB using it's file format, at the appropriate loadbang and closebang times; including the SQLLite db file in your collection you are building at the place it expects to see it (usually the dir the running binary is in..)

As i say, this is all just from memory, but really, *all* dbs must be persisted to disk to "last" and be available to a later instanced db engine.

As I recall (I am at day job and free doc access is far away)
To have "persistence" with SqlLite, you need to declare a filename to persist to : a flat file version of all the SQLLite db objects. Without this, all sqlLite work is "ephemeral": it goes away when you free the sqlLite object.
SO... by extension, if you wish to have a persisted set of data ina standalone, that is there every time the standalone is started, you will have to have the SQLLite db written down as a file somewhere, and tell SQLLite to load said DB file on startup: all this I saw long ago,in a intro to SQLLite or somesuch, so use a grain of salt here, and look it up yourself.... 

Think about it: where are those table definitions and rows of data gonna be stored in your standalone? Init into and persist from  the SQLLite DB using it's file format, at the appropriate loadbang and closebang times; including the SQLLite db file in your collection you are building at the place it expects to see it (usually the dir the running binary is in..)

As i say, this is all just from memory, but really, *all* dbs must be persisted to disk to "last" and be available to a later instanced db engine.
YMMV, PAX, hope this helps,
cfb aka j2k


this part works fine AND it works totally fine (even the select that returns my records correctly) in editor mode (not the standalone)

hello,
I have a full sqlite compliant file.

function opendb(x)
{
    sqlite.open(x,1);
}

if you are including it (the sqllite db file) in the collection of files that is used to make the standalone, where is it actually placed by the app builder? perhaps you could manually fix the location the app builder places the sqllite file? this is my only guess...a patch in a directory is not quite the same as a running standalone application, and the max app builder may not correctly place your file?

if you are including it (the sqllite db file) in the collection of files that is used to make the standalone, where is it actually placed by the app builder? perhaps you could manually fix the location the app builder places the sqllite file? this is my only guess...a patch in a directory is not quite the same as a running standalone application, and the max app builder may not correctly place your file?
just guessing, good luck.


I'm sure about that, using a global variable for all the movies located in the same folder and this part works.

I made my own workaround with a txt file containing the data.

no problem with path.
I'm sure about that, using a global variable for all the movies located in the same folder and this part works.

Could you post an example? Did you make sure that the 

Could you post an example? Did you make sure that the sqlite object was added to the standalone?


I'm sure it is included while building the standalone: I verified in support/extensions & sqlite.mxe is here.

I can extract that from my (huge) patch to make an example.

I'll do that asap (currently finishing the big installation & debugging several little things)

Hi Emmanuel,
I'm sure it is included while building the standalone: I verified in support/extensions & sqlite.mxe is here.

I can extract that from my (huge) patch to make an example.
I'll do that asap (currently finishing the big installation & debugging several little things)


Julien, did you ever figure this out or did you just end up using your js. I tested it the other day and it worked fine for me. Could be I am using OSX, just wondering if you had luck with PC.

yes I figured it out and it worked so fine.

yes I figured it out and it worked so fine.
it worked on PC finally.

sqlite works fine... but doesn't work on my standalone :-(