[sqlite] SQLDIFF problem
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 to support it now for legacy. > > > How does one invoke the sqldiff tool? I see the c file in > tool/sqldiff.c. I don't see a download for any OS at > https://www.sqlite.org/download.html > Download the source three, then from unix do "./configure; make sqldiff" or on Windows to "nmake /f makefile.msc sqldiff.exe" -- D. Richard Hipp drh at sqlite.org
[sqlite] SQLDIFF problem
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 one invoke the sqldiff tool? I see the c file in tool/sqldiff.c. I don't see a download for any OS at https://www.sqlite.org/download.html Thanks! -- --- inum: 883510009027723 sip: jungleboogie at sip2sip.info xmpp: jungle-boogie at jit.si
[sqlite] SQLDIFF problem
You're probably right.
You can try this shorter schema and get the same problem.
create table xxx("" text);
However, my point was that if SQLite3 allows it, SQLDIFF should be able to
handle it also.
Thanks.
-Original Message-
From: Tim Streater
Sent: Monday, November 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 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 the following (I tried on a
> Win7
> machine):
>
> sqlite3 xxx.db < xxx.sql
> sqldiff xxx.db xxx.db
>
> SCHEMA (xxx.sql)
>
> CREATE TABLE raw(
> "Date" TEXT,
...
> "Contact Phone Number" TEXT,
> "" TEXT
> );
Well I don't imagine it's going to like:
"" TEXT
--
Cheers -- Tim
___
sqlite-users mailing list
sqlite-users at mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] SQLDIFF problem
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
[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 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 the following (I tried on a Win7 > machine): > > sqlite3 xxx.db < xxx.sql > sqldiff xxx.db xxx.db > > SCHEMA (xxx.sql) > > CREATE TABLE raw( > "Date" TEXT, ... > "Contact Phone Number" TEXT, > "" TEXT > ); Well I don't imagine it's going to like: "" TEXT -- Cheers -- Tim
[sqlite] SQLDIFF problem
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? --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. -- D. Richard Hipp drh at sqlite.org
[sqlite] SQLDIFF problem
https://www.sqlite.org/src/info/64263ccb8f9835c6 -- D. Richard Hipp drh at sqlite.org
[sqlite] SQLDIFF problem
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 the following (I tried on a Win7 machine): sqlite3 xxx.db < xxx.sql sqldiff xxx.db xxx.db SCHEMA (xxx.sql) CREATE TABLE raw( "Date" TEXT, "Time" TEXT, "Time Zone" TEXT, "Name" TEXT, "Type" TEXT, "Status" TEXT, "Currency" TEXT, "Gross" TEXT, "Fee" TEXT, "Net" TEXT, "From Email Address" TEXT, "To Email Address" TEXT, "Transaction ID" TEXT unique, "Counterparty Status" TEXT, "Address Status" TEXT, "Item Title" TEXT, "Item ID" TEXT, "Shipping and Handling Amount" TEXT, "Insurance Amount" TEXT, "Sales Tax" TEXT, "Option 1 Name" TEXT, "Option 1 Value" TEXT, "Option 2 Name" TEXT, "Option 2 Value" TEXT, "Auction Site" TEXT, "Buyer ID" TEXT, "Item URL" TEXT, "Closing Date" TEXT, "Escrow Id" TEXT, "Invoice Id" TEXT, "Reference Txn ID" TEXT, "Invoice Number" TEXT, "Custom Number" TEXT, "Receipt ID" TEXT, "Balance" TEXT, "Address Line 1" TEXT, "Address Line 2/District/Neighborhood" TEXT, "Town/City" TEXT, "State/Province/Region/County/Territory/Prefecture/Republic" TEXT, "Zip/Postal Code" TEXT, "Country" TEXT, "Contact Phone Number" TEXT, "" TEXT );
