Re: [sqlite] Purging the mailing list roles. Was: Please Restore Your Account Access

[Paul Nash]

1200 is a modest number for a mailing list . Expect it to go up to 3-4000 as 
SQLite gets more popular. One reason for the lists popularity is the 
friendliness of the list members and their willingness to respond to basic 
SQL queries. At some stage the list could be split into two. One for wrapper 
users (tcl perl) and one for those using the C API.


Regards, Paul Nash 

Re: [sqlite] Converting ver 2 to ver 3

[Paul Nash]

Welcome to quoting hell. :-)

But I had a tcl tablecopy, and my databases all have a data definition so 
doing it the right way was real easy. But I did want to point out that the 
recommended .DUMP method is flawed.


Regards, Paul Nash
webscool.org

- Original Message - 
From: "Jay Sprenkle" <[EMAIL PROTECTED]>

To: <sqlite-users@sqlite.org>
Sent: Tuesday, April 18, 2006 1:45 AM
Subject: Re: [sqlite] Converting ver 2 to ver 3


On 4/14/06, Paul Nash <[EMAIL PROTECTED]> wrote:

I have taken the plunge and am converting from ver 2.8.16 to ver 3.

I used the .DUMP method but found a problem. My char/text fields containg 
numbers were output as pure numbers without the quotes, so that on input 
to ver 3 they were stored as integer rather than string. This is a kind of 
bug in .DUMP. Maintaining the textedness of values in columns with text 
affinity in ver 2 would ease the move to ver 3.


You could probably edit the quotes back in reasonably quickly using
any regular expression capable text editor.

[sqlite] Converting ver 2 to ver 3

[Paul Nash]

I have taken the plunge and am converting from ver 2.8.16 to ver 3.

I used the .DUMP method but found a problem. My char/text fields containg 
numbers were output as pure numbers without the quotes, so that on input to ver 
3 they were stored as integer rather than string. This is a kind of bug in 
.DUMP. Maintaining the textedness of values in columns with text affinity in 
ver 2 would ease the move to ver 3.

Regards, Paul Nash