Hi Larry,
Thanks , I knew that there is heap corruption and this is resulting due to
that.I just wanted to
confirm that whether sqlite is corrupting the heap here or not. I will use
valgrind and see.
Regards,
Ashok
On Wed, Aug 21, 2013 at 7:12 AM, Larry Brasfield
Thought I'd sent this yesterday but found it stuck in my Outbasket
today:-(
Thanks David Kai - off to look at Kexi and Dabo. Will let you know how
I get on.
I have now downloaded both Kexi Dabo.
Kexi - despite stating that a Windows version is available, when I try to
download all I get is the
Hi,
the documentation says (on http://www.sqlite.org/datatype3.html#collation):
| The expression x BETWEEN y and z is logically equivalent to two
| comparisons x = y AND x = z and works with respect to collating
| functions as if it were two separate comparisons.
However, this is not true when
I think I found a bug, tested with SQLite v3.7.15.2 and v3.7.9.
Looks like sqlite3_finalize() always returns SQLITE_OK, even if most recent
execution of prepared statement failed, which contradicts the
documentationhttp://www.sqlite.org/c3ref/finalize.html
:
If the most recent evaluation of the
On Wed, Aug 21, 2013 at 8:04 AM, Dmitry Pashkevich dpa...@gmail.com wrote:
I think I found a bug, tested with SQLite v3.7.15.2 and v3.7.9.
Looks like sqlite3_finalize() always returns SQLITE_OK, even if most recent
execution of prepared statement failed, which contradicts the
Problem
---
I feel that Clemens has brought up an important point, but I feel that rather
than notice a specific error in the implementation of BETWEEN he has
highlighted a conceptual error in SQLite. Consider this comparison:
Albert albert
It would be inappropriate to write
I'm unable to reproduce the problem using C. Maybe it is in lsqlite3.
Yes, lsqlite3 still uses the old sqlite3_prepare() API to maintain
compatibility with some legacy systems. It is long past time that it should
have changed to use sqlite3_prepare_v2().
Running Richard's example with
Oh, now I see, thanks for the explanation.
By next version of lsqlite3 do you mean next major version or next patch
release (0.9.2 presumably)? Looking forward to seeing that change.
In the meantime I just stopped relying on stmt:finalize() return code in
Lua and instead always use stmt:step()
On 8/21/2013 11:17 AM, Simon Slavin wrote:
Given that this level of implementation is correct I feel that any error in
SQLite's handling of COLLATE is closer to the expression parsing level than the
low level implementation. The low level implementation is fine. The problem
would appear to
On 08/21/2013 11:02 PM, Igor Tandetnik wrote:
On 8/21/2013 11:17 AM, Simon Slavin wrote:
Given that this level of implementation is correct I feel that any
error in SQLite's handling of COLLATE is closer to the expression
parsing level than the low level implementation. The low level
On 21 Aug 2013, at 5:02pm, Igor Tandetnik i...@tandetnik.org wrote:
I imagine you'd still want to be able to put COLLATE clause on the column
definition, as in create table t (x collate NOCASE);. How is this supposed
to work in your hypothetical new world?
It works the same as it does now,
On 8/21/2013 2:55 PM, Simon Slavin wrote:
On 21 Aug 2013, at 5:02pm, Igor Tandetnik i...@tandetnik.org wrote:
I imagine you'd still want to be able to put COLLATE clause on the column definition, as
in create table t (x collate NOCASE);. How is this supposed to work in your
hypothetical new
On 21 Aug 2013, at 8:22pm, Igor Tandetnik i...@tandetnik.org wrote:
On 8/21/2013 2:55 PM, Simon Slavin wrote:
On 21 Aug 2013, at 5:02pm, Igor Tandetnik i...@tandetnik.org wrote:
I imagine you'd still want to be able to put COLLATE clause on the column
definition, as in create table t (x
On 8/21/2013 3:26 PM, Simon Slavin wrote:
My problem is not with COLLATE in general. It's with expressions. Table
definitions are fine. Index definitions are fine. It's purely that my
understanding of the documention says that something like this
ABC COLLATE COL1 = 3F COLLATE COL2
should
Hi,
Is there a way to disable/enable specific foreign key constraint in sqlite3?
Below is the sqlserver query , would like to know similar query in sqlite 3
ALTER TABLE tablename WITH NOCHECK NOCHECK CONSTRAINT FK_Column
Thank you
-Veeresh
___
On 21 Aug 2013, at 11:49pm, veeresh kumar veeru...@yahoo.com wrote:
Is there a way to disable/enable specific foreign key constraint in sqlite3?
Below is the sqlserver query , would like to know similar query in sqlite 3
ALTER TABLE tablename WITH NOCHECK NOCHECK CONSTRAINT FK_Column
No,
On Wed, 21 Aug 2013 20:26:30 +0100
Simon Slavin slav...@bigfraud.org wrote:
My problem is not with COLLATE in general. It's with expressions.
Table definitions are fine. Index definitions are fine. It's purely
that my understanding of the documention says that something like this
ABC
Hi,
What is difference by using Colum data type as blob or Any other
(Text,INT,REAL,NUMERIC)
http://www.sqlite.org/datatype3.html
According to above link I understand “The value is a blob of data, stored
exactly as it was input”.I beleive that it what required.
Ex : Please let me know
18 matches
Mail list logo