Re: [sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables

2006-11-28 Thread Trevor Talbot
On 11/28/06, P Kishor <[EMAIL PROTECTED]> wrote: On 11/28/06, Craig Morrison <[EMAIL PROTECTED]> wrote: > Just a bit of warning, as it has bitten a few in the bum, about >3 > character extensions under the NT+ variants.. They can and will bite > you, for instance: > > dir *.sql > > Will list n

Re: [sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables

2006-11-28 Thread Will Leshner
On 11/28/06, P Kishor <[EMAIL PROTECTED]> wrote: Whether or not this is true, the fact is, in Windows (and even in Mac OS X, while using the Finder), three letter extensions mean something special. By making it '.sqlite' (or '.bobbitybob', for that matter), I hope to make my db immune from all t

Re: [sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables

2006-11-28 Thread P Kishor
On 11/28/06, Craig Morrison <[EMAIL PROTECTED]> wrote: P Kishor wrote: > On 11/28/06, John Stanton <[EMAIL PROTECTED]> wrote: >> If you use an extension greater than 3 chars you violate rules for some >> existing file systems and reduce portability. You can also make it >> difficult to parse the

[sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables

2006-11-28 Thread Craig Morrison
P Kishor wrote: On 11/28/06, John Stanton <[EMAIL PROTECTED]> wrote: If you use an extension greater than 3 chars you violate rules for some existing file systems and reduce portability. You can also make it difficult to parse the extension when it is used to type the file. we are going a bit