On 20 Mar 2014, at 11:33pm, Richard Hipp wrote:
> On Thu, Mar 20, 2014 at 7:18 PM, Tim Streater wrote:
>
>> I had a case where attempts to access a table in a user's db gave "no such
>> table", where 60 mins previously (according to the log) querying
On Thu, Mar 20, 2014 at 7:18 PM, Tim Streater wrote:
> I had a case where attempts to access a table in a user's db gave "no such
> table", where 60 mins previously (according to the log) querying that table
> gave no problems. About a day and a half later the user's
I had a case where attempts to access a table in a user's db gave "no such
table", where 60 mins previously (according to the log) querying that table
gave no problems. About a day and a half later the user's machine had what he
described as a "bad crash", so I'm suspecting he has a failing
On 20 Mar 2014, at 2:19pm, Stefano Ravagni wrote:
> I know, in facts i use a TEXT field...so you intend datagrid usually
> understand if the field is or not a DATE field showing the value in
> auto-formatted way ?
SQLite does not have a DATE datatype and does not
Thanks a lot for the fast answer & fix.
-jens
Am 20.03.2014 um 14:41 schrieb Richard Hipp :
> The ticket is now closed. Thanks for the bug report.
>
> To confirm: The simplest fix is merely to compile without -DSQLITE_DEBUG
> which will disable assert() statements, as the
I know, in facts i use a TEXT field...so you intend datagrid usually
understand if the field is or not a DATE field showing the value in
auto-formatted way ?
If this is the explanation, is not a big problemthanks for reply !
Il 20/03/2014 13.31, Kees Nuyt ha scritto:
On Wed, 19 Mar 2014
The ticket is now closed. Thanks for the bug report.
To confirm: The simplest fix is merely to compile without -DSQLITE_DEBUG
which will disable assert() statements, as the problem is an incorrect
assert(). There is nothing actually wrong with the logic, that we can
see. An alternative
Hello,
I have two sqlite databases. (db1, db2)
I try to write a trigger in db1 which inserts data to a table in db2.
In the sqlite docu there is a section about "Temp Triggers".
"...Except, it is possible to create a TEMP TRIGGER on a table in another
database."
CREATE TEMP TRIGGER ex1 AFTER
On Wed, 19 Mar 2014 14:39:39 -0700 (PDT), Stefano Ravagni
wrote:
>Hello, i'm new in SQLite develop...
>
>i'n a gridview (.NET) i visualize the data type in -MM-DD format
>
>Using others database i ever see data in format which follow culture
>setting (italian
http://www.sqlite.org/src/info/e39d032577
It appears that the fix will be to simply remove the assert() statement,
which is incorrect. But it will take some time to verify that this is the
correct fix and add new test cases, etc.
Your work-around is to simply compile without -DSQLITE_DEBUG
If I got this right, there are five types of PRAGMA:
A) some return information without making changes
B) some affect the loaded SQLite library: all connections and future
connections until the library is unloaded
C) some change the behaviour of one connection without changing anything in the
Sorry, forgot to mention that our previous version of SQLite was 3.7.17 and we
did not experience the issue there...
Am 20.03.2014 um 12:26 schrieb Jens Miltner :
> Hi,
>
> I ran into the following problem after updating the SQLite 3.8.4.1:
>
> When executing the following
Hi,
I ran into the following problem after updating the SQLite 3.8.4.1:
When executing the following (rather basic) SELECT query in a debug build of
sqlite3, this will cause an assertion to fire in whereLoopAddBtreeIndex()
(sqlite3.c, line 13411):
SELECT * FROM t1 WHERE(foo_id=5 AND name IN
On 19 Mar 2014, at 10:53pm, m.d.berce...@gmail.com wrote:
> I'm running the "pragma auto_vacuum = 'full'" a C++ code, then I go to
> SQLiteSpy, open the database and run pragma auto_vacuum in the query window
> and the result is 0.
The syntax is
PRAGMA auto_vacuum = FULL
no quotes or
Hello, i'm new in SQLite develop...
i'n a gridview (.NET) i visualize the data type in -MM-DD format
Using others database i ever see data in format which follow culture
setting (italian in this case)... but not in SQLite..
How could i solve ?
Hi there,
I'm running the "pragma auto_vacuum = 'full'" a C++ code, then I go to
SQLiteSpy, open the database and run pragma auto_vacuum in the query window
and the result is 0.
I tried "pragma auto_vacuum = 1" and still the same, it doesn't seem to
keep the setting.
I have some tables that
On Thu, 20 Mar 2014 18:05:48 +1300, Jono Poff
wrote:
> and I can't easily
> change the page size of the db either.
You may have other reasons why you can't do it easily, but
PRAGMA page_size=newpagesize;
VACUUM;
will convert to newpagesize.
--
Groet,
Hi!
SQL Maestro Group announces the release of SQLite Maestro 14.3, a complete
Windows GUI solution for SQLite database management. The new version is
immediately available at
http://www.sqlmaestro.com/products/sqlite/maestro/
Top 10 new features
=
1. Support for WITHOUT
18 matches
Mail list logo