"Michael Dupuis" <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> I have an application that uses SQLite 3.3.2 right now, and I'm
> looking to move to 3.5.2. The problem I have right now is that 3.5.2
> can't open the 3.3.2 formatted database files. I know that the file
> format changed, and then
> SQLite version 3.5.2 can read and write database files created
> by every prior version of SQLite. No exceptions.
>
Which is what I would expect. But still, I get the error that the
latest build can't read my older format. Is there anything that CAN
cause this error? My version 3.3.2 was built
"Michael Dupuis" <[EMAIL PROTECTED]> wrote:
> > SQLite version 3.5.2 can read and write database files created
> > by every prior version of SQLite. No exceptions.
> >
>
> Which is what I would expect. But still, I get the error that the
> latest build can't read my older format. Is there
> I was able to open and run "PRAGMA integrity_check" on the
> database file you sent me (off-list) on both Linux and
> MacOSX x86 using SQLite version 3.4.1 and 3.5.2. No errors.
>
> I have no idea what is causing your problem.
Ok, since it was confirmed here that there SHOULDN'T be a problem,
John:
Thanks for your feedback, but the question is: are you compiling gcc in
Linux or in Windows-32 with minGW?
The problem is that I'm using the GNU gcc compiler under Windows (minGW),
trying to build a static library as a C (not C++) project, and get a lot of
compiler error. All
Hi Scott,
My initial evaluation of this database was that it allocates memory for
each operation on the database. It returns the memory only when the
database is committed. So the behavior you see is normal.
Ray Hurst
ScottDerrick wrote:
I am using sqlite3 in a DAQ device. Data can be
Hi Scott,
Ooops..meant to say the following.
My initial evaluation of this database was that it allocates memory for
each operation on the database. It returns the memory only when the
database is CLOSED. So the behavior you see is normal.
Ray Hurst
ScottDerrick wrote:
I am using sqlite3
I need to build a DBD::SQLite package using SQLite with fts
capabilities. Can someone on this list kindly give me painless, easy
to understand instructions to do so? I need to do this on a Mac OS X
10.4 first, and then on my web host subsequently (running some flavor
of Linux, natch).
Many
There must be a way to flush what ever is being cached. Help
It's hard to believe I'm the only guy that wants to keep the database open
and just do inserts, to save CPU time.
Scott
rhurst2 wrote:
>
> Hi Scott,
>
> Ooops..meant to say the following.
>
> My initial evaluation of
Raymond Hurst <[EMAIL PROTECTED]> wrote:
> Hi Scott,
>
> Ooops..meant to say the following.
>
> My initial evaluation of this database was that it allocates memory for
> each operation on the database. It returns the memory only when the
> database is CLOSED. So the behavior you see is normal.
I'm having difficulty with Lemon's operator precedence.
Given SQLite's operator precedence table where it's presumably
interpreted with lowest precedence tokens at the top to the
highest precedence tokens at the bottom:
%left OR.
%left AND.
%right NOT.
%left IS MATCH LIKE_KW BETWEEN IN
On Nov 17, 2007, at 4:58 PM, Joe Wilson wrote:
I'm having difficulty with Lemon's operator precedence.
Given SQLite's operator precedence table where it's presumably
interpreted with lowest precedence tokens at the top to the
highest precedence tokens at the bottom:
%left OR.
%left AND.
On Nov 17, 2007, at 5:12 PM, D. Richard Hipp wrote:
On Nov 17, 2007, at 4:58 PM, Joe Wilson wrote:
I'm having difficulty with Lemon's operator precedence.
That would be a bug in lemon...
I was wrong. Turns out the bug was in the SQLite grammar
file parse.y. It was assigning the same
> > sqlite> select ~1 - ~5;
> > -8
> > sqlite> select (~1) - (~5);
> > 4
> >
>
> That would be a bug in lemon...
I guess adopting the same operator precedence as MySQL or MS SQL Server
is out of the question?
http://dev.mysql.com/doc/refman/5.0/en/operator-precedence.html
BINARY,
--- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote:
> I was wrong. Turns out the bug was in the SQLite grammar
> file parse.y. It was assigning the same precedence to the
> ones-complement ~ operator and the NOT operator. But
> ~ should have higher precedence, it seems. Fixed by
> check-in
On Nov 17, 2007, at 5:30 PM, Joe Wilson wrote:
sqlite> select ~1 - ~5;
-8
sqlite> select (~1) - (~5);
4
That would be a bug in lemon...
I guess adopting the same operator precedence as MySQL or MS SQL
Server
is out of the question?
I believe SQLite uses the same operator
I use gcc for compiling Sqlite for both Windows and Linux and others.
On Windoze I use Dev-Cpp as and IDE over the top of Mingw. You might
look at the compiler options and ensure that you are just specifying
plain vanilla ANSI C.
A.J.Millan wrote:
John:
Thanks for your feedback, but the
On Nov 17, 2007 12:07 PM, A.J.Millan <[EMAIL PROTECTED]> wrote:
>
> sources/where.c: In function `int whereClauseInsert(WhereClause*, Expr*,
> int)':
> sources/where.c:231: error: invalid conversion from `void*' to `WhereTerm*'
>
My first guess is you are trying to compile it as C++. Otherwise I
Dr. Hipp,
thanks, I'm sure I can use one or more of your solutions below to solve my
problem...
Scott
SQLite does maintain a cache of the database file. It
will hold up to 2000 pages by default. You can change
the cache size by using the "PRAGMA cache_size=N" pragma.
You can set N as small
> I believe SQLite uses the same operator precedence as the SQL standard
> requires. If I am wrong about that, please correct me and I will
> change it.
As I interpret the SQL92 standard (which I believe SQLite tries to
follow), I think all comparison operators should have the same level
of
--- Ken <[EMAIL PROTECTED]> wrote:
> SQLite documentation indicates that "!" is a unary prefix operator. Is this
> a bug?
Yeah, the docs seem to indicate that SQLite supports '!'.
http://sqlite.org/lang_expr.html:
Supported unary prefix operators are these:
-+!~NOT
If
21 matches
Mail list logo
