Greetings!
In short: sqldiff unable to formulate correct `sql` to convert slave.db into
host.db.
$ sqldiff slave.db host.db
UPDATE balancelog SET total=1500.74122892 WHERE id=1418;
$ echo "UPDATE balancelog SET total=1500.74122892 WHERE id=1418;" | sqlite3
slave.db
$ sqldiff slave.db host.d
has anyone successfully used this tool to do a reconciliation
between two tables, i am looking to do simple rec between two tables on same db
or if need be on sep db with same table name
with a key, it seems to not work very well or often gives me an error saying
that table does not exist in both
The "Limitations" section of the sqldiff documentation mentions it
doesn't handle triggers or views, but nothing about constraints. So I
expected this to report something (note how in db1, t3.ref refences t1;
in db2, it references t2):
sqlite> .open db1
sqlite> pragma foreign_keys = 1;
sqlite>
Hi,
First, thanks for the tool. It's a useful one.
But here's a quick wish-list, after using the tool in a real use case:
1) a --version switch, to know which SQLite version is statically compiled
inside sqldiff
2) in-row difference: Within a row-pair, generate a minimal UPDATE and
omits all same
Can anyone please tell me when i use SQLdiff --summary option what does the
following row means
tablename:0 changes,0 inserts , 288 deletes, 0 unchanged..
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/c
p" for usage hints.
> sqlite> CREATE TABLE test (`%` REAL);
> sqlite>
>
> $ sqldiff %.db %.db
> sqldiff: SQL statement error: unrecognized token: """
> "SELECT B.rowid, 1, -- changed row
>A.""
>
Hi,
it looks like sqldiff can't handle special characters like `%`:
$ sqlite3 %.db
SQLite version 3.13.0 2016-05-18 10:57:30
Enter ".help" for usage hints.
sqlite> CREATE TABLE test (`%` REAL);
sqlite>
$ sqldiff %.db %.db
sqldiff: SQL statement error: unrecognized token: &
On 23 March 2016 at 15:53, Alek Paunov wrote:
> Hi MM,
>
> Sorry for the late replay - I usually manage to check the list only once a
> day :-(.
>
> On 2016-03-22 16:05, MM wrote:
> ...
>
> If, by chance, you are on something Fedora based, I could give you some
>>> hints how to help our lead main
Hi MM,
Sorry for the late replay - I usually manage to check the list only once
a day :-(.
On 2016-03-22 16:05, MM wrote:
...
>> If, by chance, you are on something Fedora based, I could give you some
>> hints how to help our lead maintainer - Jan Stanek with the package
>> enhancement myself.
On 2016-03-22 13:49, Richard Hipp wrote:
> On 3/22/16, MM wrote:
>> Hello,
>> I can see sqldiff appearing here:
>>
>> https://www.sqlite.org/sqldiff.html
>>
>> and in the downloads page as part of a linux 32bit binary package.
>> Alas I don't see any 64bit package.
>
> The 32bit binaries will run
On 22 March 2016 at 13:28, Alek Paunov wrote:
> On 2016-03-22 13:49, Richard Hipp wrote:
>
>> On 3/22/16, MM wrote:
>>
>>> Hello,
>>> I can see sqldiff appearing here:
>>>
>>> https://www.sqlite.org/sqldiff.html
>>>
>>> and in the downloads page as part of a linux 32bit binary package.
>>> Alas
On 22/03/16 11:49, Richard Hipp wrote:
> On 3/22/16, MM wrote:
>> Hello,
>> I can see sqldiff appearing here:
>>
>> https://www.sqlite.org/sqldiff.html
>>
>> and in the downloads page as part of a linux 32bit binary package.
>> Alas I don't see any 64bit package.
>
> The 32bit binaries will run f
Hello,
I can see sqldiff appearing here:
https://www.sqlite.org/sqldiff.html
and in the downloads page as part of a linux 32bit binary package.
Alas I don't see any 64bit package.
Given a distro-installed 64bit sqlite binary and libs, which part of the
sources would 1 need to download only sqldi
On 3/22/16, MM wrote:
> Hello,
> I can see sqldiff appearing here:
>
> https://www.sqlite.org/sqldiff.html
>
> and in the downloads page as part of a linux 32bit binary package.
> Alas I don't see any 64bit package.
The 32bit binaries will run fine on 64bit machines.
>
> Given a distro-installed
Dear fellow SQLite-fans,
I'm still using the old version which is located at
https://www.sqlite.org/2015/sqldiff-*-3081000.zip
There seem to be some changes supporting the features 3.10 and higher brought
us.
Where can we find the newest binaries for OS X et al?
Kind regards |?Cordiali saluti
On 12/1/15, jungle Boogie wrote:
> On 30 November 2015 at 06:27, Richard Hipp wrote:
>>> Just curious. Why does SQLite allow those? Legacy (i.e.
>>> backward-compatibility)? Valid in ANSI SQL? --DD
>>
>> I don't know if it is valid ANSI SQL or not. But SQLite has always
>> allowed it, so we have
On 30 November 2015 at 06:27, Richard Hipp wrote:
>> Just curious. Why does SQLite allow those? Legacy (i.e.
>> backward-compatibility)? Valid in ANSI SQL? --DD
>
> I don't know if it is valid ANSI SQL or not. But SQLite has always
> allowed it, so we have to support it now for legacy.
How does
On 11/30/2015 06:54 PM, Richard Hipp wrote:
> On 11/30/15, Stuffer Oskar wrote:
>> Hallo,
>>
>> I'm using the sqldiff tool with the --primarykey option to generate a diff
>> between two databases
>> with the "WITHOUT ROWID" optimization.
>> sqldiff from sqlite 3.9.1 and 3.9.2 produces SQL statemen
> This mailing list strips attachments. But I wonder your suggested
> patch has not already been implemented at
> https://www.sqlite.org/src/info/e0ed4c3e376248df - can you check and
> see please.
You are right, the patch I suggested is already implemented at
https://www.sqlite.org/src/info/e0ed4
30, 2015 12:41 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] SQLDIFF problem
On 29 Nov 2015 at 18:55, tonyp at acm.org wrote:
> Here?s a report about an SQLDIFF utility problem.
> sqldiff: SQL statement error: near "IS": syntax error
>
> To repr
Hallo,
I'm using the sqldiff tool with the --primarykey option to generate a diff
between two databases
with the "WITHOUT ROWID" optimization.
sqldiff from sqlite 3.9.1 and 3.9.2 produces SQL statements with an incorrect
WHERE clause.
For example:
UPDATE tt_dati SET codCommerciale='555' WHERE
On Mon, Nov 30, 2015 at 2:50 PM, Richard Hipp wrote:
> https://www.sqlite.org/src/info/64263ccb8f9835c6
"tables with zero-length column names"
Just curious. Why does SQLite allow those? Legacy (i.e.
backward-compatibility)? Valid in ANSI SQL? --DD
On 11/30/15, Stuffer Oskar wrote:
> Hallo,
>
> I'm using the sqldiff tool with the --primarykey option to generate a diff
> between two databases
> with the "WITHOUT ROWID" optimization.
> sqldiff from sqlite 3.9.1 and 3.9.2 produces SQL statements with an
> incorrect WHERE clause.
>
>
> In the at
On 29 Nov 2015 at 18:55, tonyp at acm.org wrote:
> Here?s a report about an SQLDIFF utility problem.
> sqldiff: SQL statement error: near "IS": syntax error
>
> To reproduce, put the schema below (produced automatically by .IMPORT from a
> CSV file so don?t bother with its appearance ? but it wor
On 11/30/15, Dominique Devienne wrote:
> On Mon, Nov 30, 2015 at 2:50 PM, Richard Hipp wrote:
>
>> https://www.sqlite.org/src/info/64263ccb8f9835c6
>
>
> "tables with zero-length column names"
>
> Just curious. Why does SQLite allow those? Legacy (i.e.
> backward-compatibility)? Valid in ANSI SQL
https://www.sqlite.org/src/info/64263ccb8f9835c6
--
D. Richard Hipp
drh at sqlite.org
Here?s a report about an SQLDIFF utility problem.
sqldiff: SQL statement error: near "IS": syntax error
To reproduce, put the schema below (produced automatically by .IMPORT from a
CSV file so don?t bother with its appearance ? but it works in sqlite3) inside
some file like xxx.sql, and then do
27 matches
Mail list logo
