Re: [sqlite] Submit patch?

On Mon, Aug 12, 2013 at 10:43 PM, John McKown wrote: > I read the web site, but just didn't see a way to submit a bug-fix type > patch. The patch only affects an EBCDIC based system. Which is what I am > running on at work. I was very impressed that the code was

[sqlite] Submit patch?

I read the web site, but just didn't see a way to submit a bug-fix type patch. The patch only affects an EBCDIC based system. Which is what I am running on at work. I was very impressed that the code was already EBCDIC aware. ___ sqlite-users mailing

Re: [sqlite] ALTER TABLE ... RENAME and indices.

On Mon, Aug 12, 2013 at 4:34 PM, Scott Hess wrote: > I had been attempting to write some code like this: > > CREATE TABLE t (x); > CREATE INDEX t_x ON t(x); > -- bunch of operations over a long period. > -- now we want to run an expiration pass: > BEGIN; > ALTER TABLE t RENAME

[sqlite] Bind Parameters Documentation

Hi, In parameters section of this page http://www.sqlite.org/lang_expr.html says that "A dollar-sign followed by an identifier name also holds a spot for a named parameter with the name $. The identifier name in this case can include one or more occurrences of "::" ...". It gave me

Re: [sqlite] SQLite Input with validation and lookup

On Mon, 12 Aug 2013 10:51 +0100 (BST), "Stephen Hughes" wrote: >SQLite Input with validation and lookup >This may be a FAQ, if so please point me in the right direction, but if >not what I am looking for is a BROWSE style INPUT which will:- > - allow me to force UPPER case. > -

Re: [sqlite] SQLite Input with validation and lookup

On 12 Aug 2013, at 10:51am, Stephen Hughes wrote: > SQLite Input with validation and lookup > This may be a FAQ, if so please point me in the right direction, but if > not what I am looking for is a BROWSE style INPUT which will:- > - allow me to force UPPER case. > - set

Re: [sqlite] SQLite Input with validation and lookup

You're not exactly clear on where these restrictions come from, but, database wise, SQLite has no care or real control over what data it will retain, only the control that it will retain and attempt to protect your data. The application level is what determines what goes into the database. - To

Re: [sqlite] What can be deduced from integrity check

On Mon, Aug 12, 2013 at 11:58 AM, Jan Slodicka wrote: > > Sync action is blocking - the user has no DB access during the whole > process. The crash happened during the first user action following the > sync, > which in this case was displaying the account list in a form. >

Re: [sqlite] What can be deduced from integrity check

Thanks. > the corruption is restricted to indices, so that it can be completely > repaired by running "REINDEX" Yes, REINDEX helps at least to the extent that integrity_check succeeds. Question: How can we recognize that integrity errors refer solely to an index corruption? (Considering the

Re: [sqlite] What can be deduced from integrity check

On Mon, Aug 12, 2013 at 7:17 AM, Jan Slodicka wrote: > From time to time we receive user reports about database crashes. Problems > seem to be iOS-related. (Given the number of reports it would be a > coincidence if other platforms worked flawlessly.) > > Our testers finally

Re: [sqlite] What can be deduced from integrity check

Hi Dominique > One usually gets a link to http://www.sqlite.org/howtocorrupt.html I know, I studied it multiple times. > It doesn't seem to be the case here, but Foreign-Keys are optional Right, it is just a confusing naming scheme - all indexes have the names starting with FK_. Actually,

Re: [sqlite] What can be deduced from integrity check

On Mon, Aug 12, 2013 at 1:17 PM, Jan Slodicka wrote: > Has anybody any clue what can go wrong? I can add more details if useful or > even send corrupted DB. (Just will have to convert it to plaintext, > hopefully this does not create other problems. > One usually gets a link to

[sqlite] What can be deduced from integrity check

From time to time we receive user reports about database crashes. Problems seem to be iOS-related. (Given the number of reports it would be a coincidence if other platforms worked flawlessly.) Our testers finally managed to hit the problem, so I have a corrupted DB file. On the other hand, that's

[sqlite] SQLite Input with validation and lookup

SQLite Input with validation and lookup This may be a FAQ, if so please point me in the right direction, but if not what I am looking for is a BROWSE style INPUT which will:- - allow me to force UPPER case. - set MAXIMUM/MINIMUM values. - LOOKUP and retrieve data from a masterfile. For

Re: [sqlite] sqlite3 error string size!!!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/08/13 01:45, techi eth wrote: > What is the maximum size error string returned by sqlite3_errmsg() > function You need to make a copy of the string since it can be changed at any time, including by other threads. In practise it will usually be

[sqlite] sqlite3 error string size!!!

Hi, What is the maximum size error string returned by sqlite3_errmsg() function ? Cheers – Techi ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Suitable datatype for big integers: Introduce an EXACT datatype? (TEXT not optimized for <=64bit integers, and NUMERIC cuts the integer at the 15:th digit :( )

Hi, For big integers, INTEGER is not an option as for >64bit signed integers it leads to conversion to and storage as DOUBLE. The only reliable datatype I can see now for big integers is TEXT. This is a bit unfortunate though as for <=64bit signed integers, more optimizations would be possible.

Re: [sqlite] Can a foreign key reference a named rowid?

On Mon, Aug 12, 2013 at 9:24 AM, Dan Kennedy wrote: > On 08/12/2013 01:20 PM, Baruch Burstein wrote: > >> From the documentation for CREATE TABLE: >> >> The parent key of a foreign key constraint is not allowed to use the >> rowid. The parent key must used named

Re: [sqlite] Can a foreign key reference a named rowid?

On 08/12/2013 01:20 PM, Baruch Burstein wrote: From the documentation for CREATE TABLE: The parent key of a foreign key constraint is not allowed to use the rowid. The parent key must used named columns only. Does this mean it can or can't use a named column that is an alias for the

[sqlite] Can a foreign key reference a named rowid?

From the documentation for CREATE TABLE: The parent key of a foreign key constraint is not allowed to use the rowid. The parent key must used named columns only. Does this mean it can or can't use a named column that is an alias for the rowid? Is the problem using the rowid, or is the