[sqlite] sqlite3 file as database

Dear SQLite-users, R.Smith wrote: >".sqlite" is found somewhat, but if I had to pick one that seems most >common, it would just be the: "*.db" Firefox uses both database-extensions. '.sqlite' for sqlite3 , .db for another kind. I use .sqb for sqlite3 and .sqc for ciphered databases. When

[sqlite] sqlite3 file as database

On 15 Sep 2015, at 1:16pm, John McKown wrote: > Like the "resource fork" on the older MacOS systems? I think that OS/2 also > has "extended attributes"(?) which could be set. > https://en.wikipedia.org/wiki/Extended_file_attributes Resource forks were intended for content rather than

[sqlite] sqlite3 file as database

Like the "resource fork" on the older MacOS systems? I think that OS/2 also has "extended attributes"(?) which could be set. https://en.wikipedia.org/wiki/Extended_file_attributes > In OS/2 version 1.2 and later, the High Performance File System

[sqlite] sqlite3 file as database

At 01:07 15/09/2015, you wrote: >--- >SQUISH was a database format for storing messages in FidoNet systems. >--- Geez, I don't even recall my FidoNet node number aka address... Time must have flown by faster than I thought. -- jcd

[sqlite] sqlite3 file as database

> At 01:07 15/09/2015, you wrote: > >--- > >SQUISH was a database format for storing messages in FidoNet systems. > >--- > > Geez, I don't even recall my FidoNet node number aka address... Time > must have flown by faster than I thought. Hehehehe. Those were the good old days ... trying to

[sqlite] sqlite3 file as database

Tim Streater wrote: > I don't use any extension at all for SQLite databases. With SQLite's habit of appending "-journal" (or "-wal"/"-shm") to the end of the file name, the extension would look weird. For this reason, I tend to use names like "some-data". (I also prefer to use

[sqlite] sqlite3 file as database

On 14 Sep 2015 at 19:29, Warren Young wrote: > On Sep 14, 2015, at 8:38 AM, Stephen Chrzanowski > wrote: >> >> There are many extensions of the same .. err.. >> name(?)...value(?)..structure(?) that are completely different things. > > It?s fairly bad in the electronics engineering world,

[sqlite] sqlite3 file as database

On 2015-09-14 06:17 PM, Simon Slavin wrote: > On 14 Sep 2015, at 3:38pm, Stephen Chrzanowski wrote: > >> *.SQL appears to be a common thing for not only Structured Query >> Language, but also "Squish message base lastread pointers" -- > Whatever the heck that is. > > I use *.SQL for text files

[sqlite] sqlite3 file as database

I've decided to use .sq3 ; I'm mainly under Windows where a dedicated extension is pretty handy to launch a DB manager and sq3 doesn't seem to collide with much things around and leaves ample room for sq4, sq5, ... -- jcd

[sqlite] sqlite3 file as database

On 2015-09-14 04:07 PM, Drago, William @ CSG - NARDA-MITEQ wrote: > Why do people use .db3 for sqlite database files? In my experience .db3 is > the file extension for dBase III database files. Might I add here that if I re-read the OP's question, it might actually be that he had a DBIII file

[sqlite] sqlite3 file as database

On 14 Sep 2015, at 5:48pm, Brian Willner wrote: > You > could argue the same applies to SQLite file naming conventions as well. May work for Windows. On the Mac (and other forms of Unix) the 'file' command looks at the file header and, thanks to SQLite's consistent file headers, will

[sqlite] sqlite3 file as database

On 14 Sep 2015, at 3:38pm, Stephen Chrzanowski wrote: > *.SQL appears to be a common thing for not only Structured Query > Language, but also "Squish message base lastread pointers" -- Whatever the heck that is. I use *.SQL for text files which contain SQL commands, including the ones the

[sqlite] sqlite3 file as database

On 14 Sep 2015 at 15:07, William Drago wrote: > Why do people use .db3 for sqlite database files? In my experience .db3 is the > file extension for dBase III database files. I don't use any extension at all for SQLite databases. In any case, for the majority of them, the user chooses the name

[sqlite] sqlite3 file as database

> > *.SQL appears to be a common thing for not only Structured Query > > Language, but also "Squish message base lastread pointers" -- > Whatever the heck that is. SQUISH was a database format for storing messages in FidoNet systems. Originally designed by Scott Dudley as part of Maximus, the

[sqlite] sqlite3 file as database

sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite- > users-bounces at mailinglists.sqlite.org] On Behalf Of Simon Slavin > Sent: Saturday, September 12, 2015 11:50 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] sqlite3 file as database > > >

[sqlite] sqlite3 file as database

On Sep 14, 2015, at 1:02 PM, Tim Streater wrote: > > On 14 Sep 2015 at 19:29, Warren Young wrote: > >> We haven?t had to worry about compatibility with >> 3-character file extensions since Windows NT 3.5 and Windows 95, two decades >> ago now. > > Of course in a sensible world, OS providers

[sqlite] sqlite3 file as database

Microsoft security best practices is never to name anything .db They recommend obfuscating the function of the file and putting some strange or random (.bob) file extension. This is for when you have an active intrusion, you are not handing them what to take on a silver platter. You could argue

[sqlite] sqlite3 file as database

On Sep 14, 2015, at 8:38 AM, Stephen Chrzanowski wrote: > > There are many extensions of the same .. err.. > name(?)...value(?)..structure(?) that are completely different things. It?s fairly bad in the electronics engineering world, where it seems like half the tools use *.sch for schematics

[sqlite] sqlite3 file as database

I also should mention that before anyone harps about DB3 being reserved for DBaseIII, *.SQL appears to be a common thing for not only Structured Query Language, but also "Squish message base lastread pointers" --

[sqlite] sqlite3 file as database

That is the default extension for DBaseIII, but I've not heard any windows or linux or mac system of the past 10 years have anything to do with a DBaseIII files. There may be edge cases for old accounting applications, but it is such old technology, I do doubt it is in use for anything of new

[sqlite] sqlite3 file as database

On 12 Sep 2015, at 1:19pm, s.movaseghi at eramtec.ir wrote: > I have a database file as database.db3 but I have to use database.sqlite3 . > How can I convert the db3 file to sqlite3 file? If it is actually a SQLite database already then just rename the file. SQLite does not care what the file

[sqlite] sqlite3 file as database

Hello dears I have a database file as database.db3 but I have to use database.sqlite3 . How can I convert the db3 file to sqlite3 file? Thanks for your help sanam

[sqlite] sqlite3 file as database

sanam If renaming the file does not work; then use whatever package that can read the file to read it in and write it back out as a comma or tab delimited file. In the SQLite command line interface (CLI, implemented as SQLite3.exe) one can: "Use the ".import" command to import CSV (comma

[sqlite] sqlite3 file as database

Have you tried simply renaming the file? On Sep 12, 2015 8:29 AM, wrote: > Hello dears > I have a database file as database.db3 but I have to use database.sqlite3 . > How can I convert the db3 file to sqlite3 file? > Thanks for your help > sanam > ___