Re: [sqlite] import syntax and null values

2006-10-02 Thread Eric Matthew Finnin
myself. -Eric On 10/2/06, Fred Williams <[EMAIL PROTECTED]> wrote: > -Original Message- > From: Dennis Cote [mailto:[EMAIL PROTECTED] > Sent: Monday, October 02, 2006 1:44 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] import syntax and null values >

RE: [sqlite] import syntax and null values

2006-10-02 Thread Fred Williams
> -Original Message- > From: Dennis Cote [mailto:[EMAIL PROTECTED] > Sent: Monday, October 02, 2006 1:44 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] import syntax and null values > > > Fred Williams wrote: > > >

Re: [sqlite] import syntax and null values

2006-10-02 Thread Dennis Cote
Fred Williams wrote: Don't mean to split hairs, but... For the following, the "," is the field delimiter and '"' is the string delimiter. Although this may fly in the face of reality, an empty string should be denoted with ,"", and a null value by ,,. Who is to say whether ,, denotes an

Re: [sqlite] import syntax and null values

2006-10-02 Thread Nikki Locke
Fred Williams wrote: > Would it not be more logical to modify the .import command to place a > null value in a column where the input value is non existent? (i.e. Back > to back separators in the input) Null in, null out. Please don't do that. I have many databases with empty strings in them

RE: [sqlite] import syntax and null values

2006-10-02 Thread Fred Williams
> -Original Message- > From: Gerry Snyder [mailto:[EMAIL PROTECTED] > Sent: Monday, October 02, 2006 12:42 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] import syntax and null values > > > Fred Williams wrote: > > Would it not be more logical

Re: [sqlite] import syntax and null values

2006-10-02 Thread Dennis Cote
Fred Williams wrote: Would it not be more logical to modify the .import command to place a null value in a column where the input value is non existent? (i.e. Back to back separators in the input) Null in, null out. Fred, If you did that, there would be no way to enter an empty string

Re: [sqlite] import syntax and null values

2006-10-02 Thread Gerry Snyder
Fred Williams wrote: Would it not be more logical to modify the .import command to place a null value in a column where the input value is non existent? (i.e. Back to back separators in the input) Null in, null out. A null is not the same thing as an empty string. Some things would be

RE: [sqlite] import syntax and null values

2006-10-02 Thread Fred Williams
> -Original Message- > From: Dennis Cote [mailto:[EMAIL PROTECTED] > Sent: Monday, October 02, 2006 9:26 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] import syntax and null values > > > Rich Shepard wrote: > > On Mon, 2 Oct 2006, Eric Matthe

Re: [sqlite] import syntax and null values

2006-10-02 Thread Dennis Cote
Rich Shepard wrote: On Mon, 2 Oct 2006, Eric Matthew Finnin wrote: Could someone tell me the syntax for the .import command? I can't seem to get my null values to be recognized. .nullvalue STRING Print STRING in place of NULL values If you type '.h' you'll see the syntax of all the

Re: [sqlite] import syntax and null values

2006-10-02 Thread Rich Shepard
On Mon, 2 Oct 2006, Eric Matthew Finnin wrote: Could someone tell me the syntax for the .import command? I can't seem to get my null values to be recognized. .nullvalue STRING Print STRING in place of NULL values If you type '.h' you'll see the syntax of all the commands. Rich --

[sqlite] import syntax and null values

2006-10-02 Thread Eric Matthew Finnin
Could someone tell me the syntax for the .import command? I can't seem to get my null values to be recognized. First I created test1: CREATE TABLE [test1] ( [col1] INTEGER NOT NULL, [col2] TEXT NULL, [col3] INTEGER NULL ) The data for test1.csv has the following data: col1,col2,col3