That is not quite correct Simon. INTEGER PRIMARY KEY is always "auto
incrementing" in that a new key is always one larger than the current max() key
in the table. However, INTEGER PRIMARY KEY AUTOINCREMENT means that the key is
always one larger than *any key that has ever existed* in the
On 3 Aug 2012, at 8:32pm, Tobias Giesen wrote:
> I have a problem with this. Even when I invoke an old sqlite3
> executable, Mountain Lion still launches 3.7.12.
What are you doing to 'invoke' ?
Put the executable in a folder with your database. cd to that folder.
Igor Tandetnik wrote:
> Brandon Pimenta wrote:
>> CREATE TABLE test (
>> test_1 INTEGER PRIMARY KEY NOT NULL AUTOINCREMENT
>> );
>
> Make it
>
> INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL
>
> Though NOT NULL is redundant - PRIMARY KEY implies it.
Unlike other sql
> On ML here I can launch my version in /user/local/bin just fine.
Maybe because it's newer. Try to start the Snow Leopard version. If you
can get that done, I will be thrilled!
However I will also try putting it in /usr/local/bin next.
Cheers,
Tobias
On 8/3/2012 1:26 PM, Tobias Giesen wrote:
SQLite version 3.7.12 2012-05-14 01:41:23
Apple's version is 3.7.12 2012-04-03 19:43:07.
Well, that's the problem, then, isn't it? SQLite 3.7.12 shipped on May
14. Apple must have shipped a pre-release version of SQLite 3.7.12,
with the bug Dan
On Aug 3, 2012, at 3:32 PM, Tobias Giesen wrote:
> Apparently Apple prevents starting other versions of it and redirects
> everything to
> their current version in /usr/bin.
On ML here I can launch my version in /user/local/bin just fine.
e$ which sqlite3
Hi,
I have a problem with this. Even when I invoke an old sqlite3
executable, Mountain Lion still launches 3.7.12. Apparently Apple
prevents starting other versions of it and redirects everything to
their current version in /usr/bin.
As I wrote earlier, the same thing happened with the
> The broken.sql file works with 3.7.12 here.
So you're not using Mountain Lion ...
> SQLite version 3.7.12 2012-05-14 01:41:23
Apple's version is 3.7.12 2012-04-03 19:43:07.
> CREATE TABLE t1(x, CONSTRAINT pk_cons PRIMARY KEY(x));
Yes I can do that too. But in some larger tables, it does not
On Aug 3, 2012, at 2:33 PM, Dan Kennedy wrote:
> There was a problem similar to your description at one point, but
> it should have been fixed before the 3.7.12 release. What do you
> get from the shell command "SELECT sqlite_source_id();" on
> Mountain Lion?
e$
On 08/03/2012 11:33 PM, Tobias Giesen wrote:
Hello,
thanks for the replies!
A sample Mountain-unreadable file is here:
http://www.superflexible.com/broken.sql
Works fine under Snow Leopard.
I get the same results when using my own application as when using
/usr/bin/sqlite3. So, we can
Sounds like a plan!! Many thanks!
Please excuse the shortness of this mail, as I am sending it from my phone. If
necessary, I will send more details soon.
Warmest mobile regards from
Tobias Giesen
On 03.08.2012, at 19:12, Simon Slavin wrote:
>
> On 3 Aug 2012, at
On 3 Aug 2012, at 5:48pm, Tobias Giesen wrote:
> yes I can run the dump on Snow Leopard, but many of my customers do not
> have Snow Leopard any more and they do not want to send me their files
> for conversion.
>
> The problem is that hundreds of customers need to
Hello,
yes I can run the dump on Snow Leopard, but many of my customers do not
have Snow Leopard any more and they do not want to send me their files
for conversion.
The problem is that hundreds of customers need to convert/fix their
files. It must be done under Mountain only and I have to
On 3 Aug 2012, at 5:33pm, Tobias Giesen wrote:
> And a .dump results in an incomplete dump, otherwise it would be easy
> for me to convert/fix the database.
>
> The .dump does not give me any of the contents of the table DATA.
You should definitely be able run .dump
Hello,
thanks for the replies!
A sample Mountain-unreadable file is here:
http://www.superflexible.com/broken.sql
Works fine under Snow Leopard.
I get the same results when using my own application as when using
/usr/bin/sqlite3. So, we can concentrate on the sqlite3 command line tool.
I
Simon Slavin wrote:
> All INTEGER PRIMARY KEY columns automatically have AUTOINCREMENT. You should
> not specify it yourself.
There's a subtle difference in behavior with and without AUTOINCREMENT keyword.
See
http://www.sqlite.org/autoinc.html
--
Igor Tandetnik
Brandon Pimenta wrote:
> CREATE TABLE test (
> test_1 INTEGER PRIMARY KEY NOT NULL AUTOINCREMENT
> );
Make it
INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL
Though NOT NULL is redundant - PRIMARY KEY implies it.
--
Igor Tandetnik
On 08/03/2012 09:33 PM, Tobias Giesen wrote:
Hello,
here's a problem that's puzzling me.
I have one particular type of database that has become unreadable on
the new Mac OS 10.8. It must be related to the SQL structure. The error
I get is "database disk image is malformed". But the same file,
On 3 Aug 2012, at 4:53pm, Brandon Pimenta wrote:
> When using the SQL query
>
> CREATE TABLE test (
> test_1 INTEGER PRIMARY KEY NOT NULL AUTOINCREMENT
> );
>
> or
>
> CREATE TABLE test (
> test_1 INTEGER PRIMARY KEY NOT NULL AUTO_INCREMENT
> );
>
> I will get
When using the SQL query
CREATE TABLE test (
test_1 INTEGER PRIMARY KEY NOT NULL AUTOINCREMENT
);
or
CREATE TABLE test (
test_1 INTEGER PRIMARY KEY NOT NULL AUTO_INCREMENT
);
I will get the same error.
On Fri, Aug 3, 2012 at 12:46 PM, Kees Nuyt wrote:
> On Fri, 3 Aug 2012
Good day,
I had a similar sounding issue on 2 different flavours of Windows.
The problem was an over active anti-virus program.
Adam
On Fri, Aug 3, 2012 at 11:45 AM, Simon Slavin wrote:
>
> On 3 Aug 2012, at 3:33pm, Tobias Giesen wrote:
>
>> I
On Fri, 3 Aug 2012 10:08:56 -0300, Brandon Pimenta
wrote:
>I cannot use AUTO_INCREMENT. Here's my query:
>
>CREATE TABLE test (
>test_1 NOT NULL AUTO_INCREMENT
>);
>
>Running this query gives me "SQL error: near "AUTO_INCREMENT": syntax
>error". What does this mean?
Brandon Pimenta wrote:
> I cannot use AUTO_INCREMENT. Here's my query:
>
> CREATE TABLE test (
> test_1 NOT NULL AUTO_INCREMENT
> );
First, it's AUTOINCREMENT, without underscore. Second, it can only appear after
PRIMARY KEY.
> Running this query gives me "SQL
Don't you have to specify a column type for test_1?
RobR
-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]
On Behalf Of Brandon Pimenta
Sent: Friday, August 03, 2012 9:09 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] AUTO_INCREMENT
Hello,
here's a problem that's puzzling me.
I have one particular type of database that has become unreadable on
the new Mac OS 10.8. It must be related to the SQL structure. The error
I get is "database disk image is malformed". But the same file, on
Snow Leopard, works fine.
The SQLite
I cannot use AUTO_INCREMENT. Here's my query:
CREATE TABLE test (
test_1 NOT NULL AUTO_INCREMENT
);
Running this query gives me "SQL error: near "AUTO_INCREMENT": syntax
error". What does this mean?
SQLite 3.6.12
___
sqlite-users mailing list
Hello,
here's a problem that's puzzling me.
I have one particular type of database that has become unreadable on
the new Mac OS 10.8. It must be related to the SQL structure. The error
I get is "database disk image is malformed". But the same file, on
Snow Leopard, works fine.
The SQLite
27 matches
Mail list logo