On Aug 6, 2012, at 4:51 PM, Simon Slavin wrote:
> On 6 Aug 2012, at 7:48pm, Doug Currie wrote:
>
>> ~ e$ /usr/local/bin/sqlite3 :memory: 'SELECT sqlite_source_id()'
>> 2012-05-14 01:41:23 8654aa9540fe9fd210899d83d17f3f407096c004
>
> I think this copy has been installed by something else.
Yes
On 6 Aug 2012, at 7:48pm, Doug Currie wrote:
> ~ e$ /usr/local/bin/sqlite3 :memory: 'SELECT sqlite_source_id()'
> 2012-05-14 01:41:23 8654aa9540fe9fd210899d83d17f3f407096c004
I think this copy has been installed by something else. I don't think it comes
with Apple's distribution of Mountain L
eral Discussion of SQLite Database
Subject: EXT :Re: [sqlite] sqlite3 database unreadable on Mountain Lion
On Aug 6, 2012, at 8:26 AM, Simon Slavin wrote:
> So either Apple has made a change between versions, or we have different
> paths.
I use fully qualified pathnames here:
~ e$ /usr
On Aug 6, 2012, at 8:26 AM, Simon Slavin wrote:
> So either Apple has made a change between versions, or we have different
> paths.
I use fully qualified pathnames here:
~ e$ /usr/bin/sqlite3 :memory: 'SELECT sqlite_source_id()'
2012-04-03 19:43:07 86b8481be7e7692d14ce762d21bfb69504af
~
On 6 Aug 2012, at 1:04pm, Chris Smith wrote:
> Running Mountain Lion, I got:
> 2012-06-11 02:05:22 f5b5a13f7394dc143aa136f1d4faba6839eaa6dc
>
> for:
> sqlite3 :memory: 'SELECT sqlite_source_id()'
For comparison, in a pre-release version of Mountain Lion I get
$ which sqlite3
/usr/bin/sqlite3
On Mon, Aug 6, 2012 at 8:04 AM, Chris Smith wrote:
> Running Mountain Lion, I got:
> 2012-06-11 02:05:22 f5b5a13f7394dc143aa136f1d4faba6839eaa6dc
>
Have you upgraded your SQLite? Because Doug Currie at
http://www.mail-archive.com/sqlite-users@sqlite.org/msg71932.html gives a
very different ver
Running Mountain Lion, I got:
2012-06-11 02:05:22 f5b5a13f7394dc143aa136f1d4faba6839eaa6dc
for:
sqlite3 :memory: 'SELECT sqlite_source_id()'
On Mon, Aug 6, 2012 at 7:26 AM, Richard Hipp wrote:
> On Fri, Aug 3, 2012 at 10:33 AM, Tobias Giesen >wrote:
>
> > Hello,
> >
> > here's a problem that
On Fri, Aug 3, 2012 at 10:33 AM, 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".
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. type
./sqlite3 databasena
> 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 re
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
/usr/local/bin/sqlite3
e$ sqlite3
SQLi
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 sqlite3.
> 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$ /usr/bin/sqlite3
SQLite version
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 concent
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 5:48pm, Tobias Giesen wrot
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 convert/fix their
> files. I
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 autom
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 using the shell tool in you
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 not
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, o
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 have one particular type of database that has beco
On 3 Aug 2012, at 3:33pm, Tobias Giesen wrote:
> 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.
>
> Th
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 version
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 version
26 matches
Mail list logo
