Re: [sqlite] SQLite.so dynamic library-linux

@Pavel Apologies. I just hit reply and thought it would have gone to the right place. A 3rd party company doesn't compile my code. It's an API interface to the SQLite library so people can use SQLite in LabVIEW. I don't have linux (never had linux) and buying a load of hardware isn't really

Re: [sqlite] SQLite.so dynamic library-linux

Oh, and BTW, reply to the whole list, not to me only, please. Pavel On Fri, Mar 18, 2011 at 9:41 PM, Pavel Ivanov wrote: > I still don't understand what you do. If you don't have Linux, you > don't compile on Linux and you don't test on Linux then why do you > need library

Re: [sqlite] Unique index versus unique constraint

On 18/03/2011, at 8:58 PM, Paul van Helden wrote: > Another solution that ocurred to me is to check for "sqlite_autoindex_" in > the name field of pragma index_list(tablename). Can I simply assume that > unique indexes named sqlite_autoindex_* cannot be dropped? Automatic indexes have no "SQL"

Re: [sqlite] WebSql question

Yes, that one did it. Iterating on arrays by their factors. Thanks. On Fri, Mar 18, 2011 at 11:05 AM, H. Phil Duby wrote: > Nothing to do with SQLite, but ... > > ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] Contributing VC 9 and 10 project/solution files

Hi, I've created project/solution files for VC 9 and 10 that build SQLite3 DLLs in multiple configurations (Debug/Release, Win32/x64). They also set proper preprocessor macros when building the sources (taken from mkdll.sh). I would like to contribute them if there is interest. I think it makes

Re: [sqlite] WebSql question

Nothing to do with SQLite, but ... On Fri, Mar 18, 2011 at 4:01 AM, Matt Young wrote: > > Here is my Javascript code, it works.  Except I have to know the table field > names within the javascript code itself: This little phrase: > > results.rows[i].f1 > > f1 is a field

Re: [sqlite] SQLite.so dynamic library-linux

What's wrong with compiling SQLite library by yourself with all parameters you need? Why do you need cross-compiler for that? What's wrong with compiler on your linux box? Pavel On Fri, Mar 18, 2011 at 10:54 AM, Udon Shaun wrote: > Hi Peeps. > I've noticed that the SQLite

[sqlite] SQLite.so dynamic library-linux

Hi Peeps. I've noticed that the SQLite site no longer posts the linux x32 so library (only the windows ones) which is a bit of a pain because I compile only in windows. Does anyone have a linux x32 build (sqlite 3.7.5) with the following compiler options? Or can create one for me?

Re: [sqlite] Determining deepest descendents of parent records from one table

I think you should limit yourself to one table, at least for the purpose of parent<->child relationships. I am working on a similar problem right now. (I started with sqlite, but moved to mysql for reasons outside of this problem scope.) My solution, which performs fine, is as follows: I put

[sqlite] Determining deepest descendents of parent records from one table

I have 5 tables that store records for 5 different types of documents. Each type of document can be a descendent of a document in one of the other tables. For example, let's call the tables A, B, C, D and E. If you create a record in A, and then create a record in B, you can associate the

Re: [sqlite] Unique index versus unique constraint

On 18 Mar 2011, at 9:58am, Paul van Helden wrote: > So my problem is, I need to know how the unique requirement was created in > the first place in order to get rid of it in the appropriate manner. > > One solution would be to parse the SQL field in sqlite_master to look for > the constraint.

[sqlite] WebSql question

Here is my Javascript code, it works. Except I have to know the table field names within the javascript code itself: This little phrase: results.rows[i].f1 f1 is a field name, I have to know this in the call. Yes I know indexDB is coming, but is there a workaround for this? I want to scoop up

[sqlite] Unique index versus unique constraint

Hi All, When I create a table and specify a unique constraint, a unique index is automatically created. This index cannot be dropped, so the only way to get rid of the uniqueness is to recreate the table without the constraint. No problem. When I create a table without the unique constraint, I

Re: [sqlite] Tell if index is used for query?

On 18 Mar 2011, at 6:51am, Michael Parker wrote: >> http://www.sqlite.org/datatype3.html > > Ahh, interesting. Since the date granularity is days and does't > include the time, I'll be changing date and uid to use REAL and TEXT, > respectively. INTEGER and TEXT ? Or did I misunderstand you.

Re: [sqlite] Tell if index is used for query?

Hi Simon, thanks for the quick and thorough reply! Inlining my response... On Thu, Mar 17, 2011 at 11:27 PM, Simon Slavin wrote: > > On 18 Mar 2011, at 6:06am, Michael Parker wrote: > >> CREATE TABLE CalendarData ( >>  date date NOT NULL, >>  uid char(40) NOT NULL, >>  json

Re: [sqlite] UTF-8 strings & ICU

On 18 Mar 2011, at 5:07am, ashish yadav wrote: > Can you please also provide some code sample for same ? > > i am not able to understand, your point "When a custom collation is > registered, it may indicate whether it wants its strings in UTF-8, UTF-16 or > either." The ICU extension for

Re: [sqlite] Tell if index is used for query?

On 18 Mar 2011, at 6:06am, Michael Parker wrote: > CREATE TABLE CalendarData ( > date date NOT NULL, > uid char(40) NOT NULL, > json text NOT NULL, > PRIMARY KEY (date, uid) > ); > > I just want to confirm that the index for the primary key efficiently > handles queries using WHERE or

[sqlite] Tell if index is used for query?

Hi all, Sorry in advance about this newbish question. Rest assured I've checked the FAQ, Wiki, and Googled before coming to you now empty-handed. I have a really simple schema: CREATE TABLE CalendarData ( date date NOT NULL, uid char(40) NOT NULL, json text NOT NULL, PRIMARY KEY (date,