Re: [sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables
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 not only *.sql files, but *.sqlite too. > > Imagine: > > del *.sql fair warning, but totally pointless -- 'del *.s*' will delete all your sql files as well, and so will 'del *.??l*' and and host of other variations. There are many ways of harming oneself, but picking on arbitrarily long extensions as a particularly dangerous one is baseless, afaik. Note the lack of a trailing wildcard in his example. That was not a typo. The issue there is due to short filenames being matched; the related configuration setting is documented here: http://support.microsoft.com/kb/164351 Recently, I read somewhere (forget the link... should be easy to search for) -- apparently some file extensions are registered within Windows as special files that need to be indexed on every change. One of those extensions is '.dbd' (I could be wrong about the particular extension... but, for the sake of argument, let's just assume it is '.dbd'). So, every time your database changes even a little bit, the OS wants to index it... this person who discovered this phenomenon, claimed it was causing a performance bottleneck. Windows XP's System Restore tracks and journals the contents of certain filetypes in realtime. I don't have a link for the filetypes handy though. There's a similar issue with some of the desktop search applications trying to index file contents. 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 this. Actually, even better might be not having any extension at all. It's not that 3 letter extensions in the abstract are special (both OSes can handle extensions of any length), it's just that most of the logical 1-3 letter extensions have already been used by someone else. I tend to choose long extensions for the same reason. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables
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 this. Actually, even better might be not having any extension at all. Actually, Mac OS X (and that includes the Finder) has no restriction on the length of the extension. Many applications use very long extensions, in fact. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables
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 extension when it is used to type the file. > > we are going a bit off-thread here, but violating the file system rule > (in this case, Windows) is precisely why I use an extension greater > that 3 chars. For example, .db extension is used by several other > programs -- Windows itself uses .db extension for thumbnails it > generates for pictures inside a folder. I want to get above that > riff-raff. The stupid system just lists my databases as "SQLITE File." > Good enough for me. > > As far as portability is concerned -- my world revolves around Unixes, > in particular Mac OS X, some Linux variants, and Windows. I have never > had any portability issues with foo.sqlite. > >> >> In medecine the Hippocratic Oath requires "First, do no harm". Not a >> bad principle for IT design also. > > I think, in good health, the first principle should be, don't expose > yourself to ills. By making my extension illegible to anything but > SQLite, I am not even getting in the fray. Since we're already off-topic. :-D I'm sure you are already aware of this, just pointing it out in context so those that aren't have a heads up. 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 not only *.sql files, but *.sqlite too. Imagine: del *.sql Deleting all your *.sqlite files. Whoopsie.. fair warning, but totally pointless -- 'del *.s*' will delete all your sql files as well, and so will 'del *.??l*' and and host of other variations. There are many ways of harming oneself, but picking on arbitrarily long extensions as a particularly dangerous one is baseless, afaik. Recently, I read somewhere (forget the link... should be easy to search for) -- apparently some file extensions are registered within Windows as special files that need to be indexed on every change. One of those extensions is '.dbd' (I could be wrong about the particular extension... but, for the sake of argument, let's just assume it is '.dbd'). So, every time your database changes even a little bit, the OS wants to index it... this person who discovered this phenomenon, claimed it was causing a performance bottleneck. 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 this. Actually, even better might be not having any extension at all. -- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation https://edu.osgeo.org/ --- collaborate, communicate, compete - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] OT: filenaming conventions -- was: Re: [sqlite] Saving tables
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 off-thread here, but violating the file system rule (in this case, Windows) is precisely why I use an extension greater that 3 chars. For example, .db extension is used by several other programs -- Windows itself uses .db extension for thumbnails it generates for pictures inside a folder. I want to get above that riff-raff. The stupid system just lists my databases as "SQLITE File." Good enough for me. As far as portability is concerned -- my world revolves around Unixes, in particular Mac OS X, some Linux variants, and Windows. I have never had any portability issues with foo.sqlite. In medecine the Hippocratic Oath requires "First, do no harm". Not a bad principle for IT design also. I think, in good health, the first principle should be, don't expose yourself to ills. By making my extension illegible to anything but SQLite, I am not even getting in the fray. Since we're already off-topic. :-D I'm sure you are already aware of this, just pointing it out in context so those that aren't have a heads up. 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 not only *.sql files, but *.sqlite too. Imagine: del *.sql Deleting all your *.sqlite files. Whoopsie.. -- Craig Morrison =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://pse.2cah.com Controlling pseudoephedrine purchases. http://www.mtsprofessional.com/ A Win32 email server that works for You. - To unsubscribe, send email to [EMAIL PROTECTED] -
