On Oct 3, 2008, at 9:58 PM, Gavin Kistner wrote:
> I love railroad diagrams, and these are particularly attractive. Nice!
Sorry for the triple message spam. Apparently I fail at email.
___
sqlite-users mailing list
sqlite-users@sqlite.org
h
On Oct 3, 2008, at 8:48 AM, D. Richard Hipp wrote:
> http://www.sqlite.org/draft/syntaxdiagrams.html
> http://www.sqlite.org/draft/syntax.html
>
> Comments, criticism, and error reports are welcomed - particularly if
> they are received in time to be addressed prior to the release of
> 3.6.4, curre
I love railroad diagrams, and these are particularly attractive. Nice!
A couple suggestions:
The diagrams are read most easily left to right; rolling to a new line
greatly reduces the utility, IMO. Roughly 7% of the 'net is still
using 800x600, and surely far less of tech savvy audience.
I
On Oct 3, 2008, at 8:48 AM, D. Richard Hipp wrote:
> http://www.sqlite.org/draft/syntaxdiagrams.html
> http://www.sqlite.org/draft/syntax.html
>
> Comments, criticism, and error reports are welcomed - particularly if
> they are received in time to be addressed prior to the release of
> 3.6.4, curre
On Sep 23, 2008, at 12:06 AM, Robert Simpson wrote:
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Kistner
>> Sent: Monday, September 22, 2008 9:45 PM
>> To: General Discussion of SQLite Database
&g
On Sep 23, 2008, at 12:06 AM, Robert Simpson wrote:
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Kistner
>> Sent: Monday, September 22, 2008 9:45 PM
>> To: General Discussion of SQLite Database
&g
On Sep 22, 2008, at 11:17 PM, Roger Binns wrote:
> Gavin Kistner wrote:
>> Mostly I'm sharing this as a curiosity, though I'm quite interested
>> if
>> anyone has a suggestion on why
>> this might be so much slower on a roughly equivalent machine
>> d
On Sep 22, 2008, at 11:03 PM, P Kishor wrote:
> I am assuming you have good reason to not just ATTACH the old db to
> the new db and INSERT INTO new_table SELECT * FROM old_db.old_table
Partially ignorance about that, and partially because I want to use
the ORMs involved with the DB to ensure th
(Right off the bat, let me say that I'm not sure if the problem here
is Sequel, sqlite3-ruby, or
sqlite. Just in case...)
I have a Ruby script to migrate data from an old sqlite DB to a new
schema. It's quite simple, selecting rows from db 1 and creating
records in db 2. (A rough representat
On Sep 12, 2008, at 10:16 AM, Dennis Cote <[EMAIL PROTECTED]> wrote:
> Gavin Kistner wrote:
>
>> Given that it's possible (if moderately insane) and legal(?) to
>> have a
>> column name with a backtick in it, then displaying "`foo`" as the
On Sep 12, 2008, at 3:40 PM, Dennis Cote <[EMAIL PROTECTED]> wrote:
> Gavin Kistner wrote:
>>>
>>>
>>> (As an aside, here's a fun bug: try "select * from perverse" and see
>>> if you can guess what will be shown in sqlite.)
>>>
Ack, trying again with subscribed address.
--
(-, /\ \/ / /\/
On Sep 12, 2008, at 2:46 PM, Gavin Kistner <[EMAIL PROTECTED]> wrote:
> On Sep 12, 2008, at 10:16 AM, Dennis Cote <[EMAIL PROTECTED]>
> wrote:
>
>> Gavin Kistner wrote:
>>
>>> Given tha
On Sep 11, 2008, at 11:44 AM, D. Richard Hipp wrote:
> On Sep 11, 2008, at 1:11 PM, Gavin Kistner wrote:
>
>> So I ask again: can the inclusion of backticks in the column name
>> returned as the result for certain select statements be considered a
>> bug?
>
> In the a
On Sep 11, 2008, at 10:49 AM, Igor Tandetnik wrote:
> Gavin Kistner <[EMAIL PROTECTED]> wrote:
>> The presence of backticks in the column header name is causing the
>> ORB
>> library I'm working with to think that the name of the column is
>> &qu
> SQLite version 3.5.6
> Enter ".help" for instructions
> sqlite> create table 'foo' (bar 'text');
> sqlite> insert into 'foo' values ('a');
> sqlite> .headers on
> sqlite> select * from foo;
> bar
> a
> sqlite> select "bar" from foo;
> bar
> a
> sqlite> select `bar` from foo;
> bar
> a
> sqlite> s
15 matches
Mail list logo
