[sqlite] sqlite3 file as database

[Klaas V]

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 sqlite4 is 
released I can go on
 with .sqd and .sqe. Like someone stated earlier: .sql is "reserved" for 
SQL-scripts, because 
 TextWrangler does some very useful syntax-checking for this filetype.

Kind regards |?Cordiali saluti | Vriendelijke groeten | Freundliche Gr?sse,
Klaas `Z4us` V ?- OrcID -0001-7190-2544

[sqlite] sqlite3 file as database

[Simon Slavin]

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 meta-data.  But the Mac 
always had the Creator/Type system that was mentioned earlier in the thread.  
They were each four characters long, so you'd have a Creator/type of

ttxt/text = a text file created by 'TeachText' (equivalent of NOTEPAD)
mpnt/jpeg = an image file in JPEG format created by MacPaint
CDrw/jpeg = an image file in JPEG format created by Corel Draw

etc..

The creator told the operating system which application should be launched by 
default to open the file.  The type told all applications what they'd find if 
they opened the file, and using that they could decide whether they should be 
opening the file at all.

The filename was completely ignored by the original MacOS.  It paid attention 
only to those settings.  They weren't part of the filename and you needed to 
run a little utility to change them, which meant that the sort of users who 
would mess things up by changing a file extension were not able to mess them up.

It was an excellent system, far better than just having a three character file 
extension.

Simon.

[sqlite] sqlite3 file as database

[John McKown]

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
 was designed
with extended attributes in mind, but support for them was also
retro-fitted on the FAT
 filesystem of DOS.
For compatibility with other operating systems using a FAT partition, OS/2
attributes are stored inside a single file "EA DATA. SF" located in the
root directory. This file is normally inaccessible when an operating system
supporting extended attributes manages the disk, but can be freely
manipulated under, for example, DOS. Files and directories having extended
attributes use one or more clusters
 inside this file. The
logical cluster number of the first used cluster is stored inside the
owning file's or directory's directory entry
. These two
bytes are used for other purposes on the FAT32 filesystem, and hence OS/2
extended attributes cannot be stored on this filesystem.

Parts of OS/2 version 2.0 and later such as the Workplace Shell
 uses several standardized
extended attributes (also called *EAs*) for purposes like identifying the
filetype, comments, computer icons
 and keywords about the file.
Programs written in the interpreted language Rexx
 store an already parsed
 version of the code as an extended
attribute, to allow faster execution.


On Mon, Sep 14, 2015 at 2:02 PM, Tim Streater  wrote:

> 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, where it seems like
> > half the tools use *.sch for schematics and *.brd/pcb for printed circuit
> > board layouts, but none of the tools agree on the format of the actual
> file
> > data.  If you have two such apps installed, you have to make a hard
> choice
> > about which app becomes the default to open such files, and occasionally
> have
> > to fix it when updating the other app, as it takes over the extensions
> again.
> >
> > This widespread unwillingness to get beyond the 8.3 limits, particularly
> on
> > Windows, is annoying.  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 would all have implemented a
> common metadata API, and no one would need or use extensions.
>
> --
> Cheers  --  Tim
>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
>


-- 

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

[sqlite] sqlite3 file as database

[Jean-Christophe Deschamps]

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

[Keith Medcalf]

> 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 get just a few more bps 
out of a serial modem link.  I still have a couple each of the original 
National Semiconductor 16550A, 16550AF, and 16550AFN that I got as samples ... 

1:148/218 1:250/714 1:250/702 1:250/703 1:250/750

[sqlite] sqlite3 file as database

[Clemens Ladisch]

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 journal_mode=truncate, so that users aren't
surprised when a -journal file shows up, and try to do clever things
to it.)


Regards,
Clemens

[sqlite] sqlite3 file as database

[Tim Streater]

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, where it seems like
> half the tools use *.sch for schematics and *.brd/pcb for printed circuit
> board layouts, but none of the tools agree on the format of the actual file
> data.  If you have two such apps installed, you have to make a hard choice
> about which app becomes the default to open such files, and occasionally have
> to fix it when updating the other app, as it takes over the extensions again.
>
> This widespread unwillingness to get beyond the 8.3 limits, particularly on
> Windows, is annoying.  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 would all have implemented a common 
metadata API, and no one would need or use extensions.

--
Cheers  --  Tim

[sqlite] sqlite3 file as database

[R.Smith]

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 which contain SQL commands, including the ones the 
> SQLite tool generates from '.dump'.
>
> I don't have a good answer about what extension to use for SQLite databases.  
> At the moment I seem to favour using the extension '.sqlite' but I'd be hard 
> pressed to make an argument for it.  I wonder what I'll do when SQLite4 comes 
> along.

Yeah - I might add that sqlite is very often used as an application file 
format, which results in a myriad of extensions out there.

There is no noticeable convention. I happen to see it lots because when 
developing the search functions, I use SQLitespeed and just point the 
search tool to the c:\users\xxx\appdata\ folder on any new system, enter 
*.* as the search text, tick "include sub-folders" and after about a 
minute I see a list of every SQLite database in the system. (Well, in 
Appdata anyway).

There are usually loads, but I have never noticed any convention or 
extension being more prevalent than any other. It's usually just random 
- and where duplications occur, they usually belong to the same system.

".sqlite" is found somewhat, but if I had to pick one that seems most 
common, it would just be the:  "*.db"
(Security-win, I know)


For reference, I just checked this pc (as described above) and these are 
all the valid SQLite DB's in Appdata with their extensions:
(Your experience may differ)

C:\Users\R.Smith\AppData\Local\Adobe\OOBE\opm.db
C:\Users\R.Smith\AppData\Local\EvernoteNW\cookies
C:\Users\R.Smith\AppData\Local\EvernoteNW\Local Storage\file__0.localstorage
C:\Users\R.Smith\AppData\Local\EvernoteNW\Web Data
C:\Users\R.Smith\AppData\Local\Evernote\Evernote\Databases\rsmith386.exb
C:\Users\R.Smith\AppData\Local\Mozilla\Firefox\Profiles\tvs0coxp.default\OfflineCache\index.sqlite
C:\Users\R.Smith\AppData\Local\Steam\htmlcache\Cookies
C:\Users\R.Smith\AppData\Local\Steam\htmlcache\Local 
Storage\https_www.youtube.com_0.localstorage
C:\Users\R.Smith\AppData\Local\Steam\htmlcache\Local 
Storage\http_steamcommunity.com_0.localstorage
C:\Users\R.Smith\AppData\Local\Temp\Test1e499fd04-6213-4da6-97a3-209da4fd29eb.prmdc
C:\Users\R.Smith\AppData\Roaming\Adobe\Bridge CS6\Cache\data\store
C:\Users\R.Smith\AppData\Roaming\Atlantic\AIDB_SysData.cdb
C:\Users\R.Smith\AppData\Roaming\Atlantic\AIDB_SysData_Backup.cdb
C:\Users\R.Smith\AppData\Roaming\Dropbox\instance1\aggregation.dbx
C:\Users\R.Smith\AppData\Roaming\Dropbox\instance1\config.db
C:\Users\R.Smith\AppData\Roaming\FDM\SysData\FDM_LocData.rdb
C:\Users\R.Smith\AppData\Roaming\FDM\SysData\FDM_Logs.rdb
C:\Users\R.Smith\AppData\Roaming\FileZilla\queue.sqlite3
C:\Users\R.Smith\AppData\Roaming\IPView\SysData\Data\IPDB_CalcData.idb
C:\Users\R.Smith\AppData\Roaming\IPView\SysData\Data\IPDB_ImptData.idb
C:\Users\R.Smith\AppData\Roaming\IPView\SysData\Data\IPDB_ImptData_Old_Planners_Backup.idb
C:\Users\R.Smith\AppData\Roaming\IPView\SysData\Data\IPDB_StdLists.idb
C:\Users\R.Smith\AppData\Roaming\IPView\SysData\Data\IPDB_UserData.idb
C:\Users\R.Smith\AppData\Roaming\IPView\Sys_Cache.cdb
C:\Users\R.Smith\AppData\Roaming\Listary\UserData\History_v2.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\content-prefs.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\cookies.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\evernote_webclipper.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\formhistory.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\healthreport.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\permissions.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\places.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\reading-list.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\storage\default\fileC++Projects+Unity+Temp+TestProj1+tpWebGL+index.html\idb\2083995541%s2fFbid.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\storage\default\https+++google.github.io\idb\3823323449mbvd.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\storage\default\https+++uplay.ubi.com\idb\533021264u3pVlya.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\storage\default\https+++www.maxmind.com\idb\581034704_b_Dmsmwaip.sqlite
C:\Users\R.Smith\AppData\Roaming\Mozilla\Firefox\Profiles\tvs0coxp.default\storage\permanent\chrome\idb\2918063365piupsah.sqlite

[sqlite] sqlite3 file as database

[Jean-Christophe Deschamps]

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

[R.Smith]

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 which he wanted to export to SQlite, and 
maybe not a .db3 file that was already an sqlite file.

[sqlite] sqlite3 file as database

[Simon Slavin]

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 
identify it for you:

178:~ simon$ sqlite3 ~/Desktop/test
SQLite version 3.8.10.2 2015-05-20 18:17:19
Enter ".help" for usage hints.
sqlite> CREATE TABLE a(b INT);
sqlite> .quit

178:~ simon$ file ~/Desktop/test
/Users/simon/Desktop/test: SQLite 3.x database
178:~ simon$ 

Simon.

[sqlite] sqlite3 file as database

[Simon Slavin]

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 tool generates from '.dump'.

I don't have a good answer about what extension to use for SQLite databases.  
At the moment I seem to favour using the extension '.sqlite' but I'd be hard 
pressed to make an argument for it.  I wonder what I'll do when SQLite4 comes 
along.

Simon.

[sqlite] sqlite3 file as database

[Tim Streater]

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 and they have no need to know that 
it's an SQLite database.

--
Cheers  --  Tim

[sqlite] sqlite3 file as database

[Keith Medcalf]

> > *.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 format was 
eventually widely used because of its speed and relatively efficient design 
compared to other message-store formats.  Squish was also an application of the 
same name for processing messages in and out of Squish message stores and a 
standard FidoNet inbound/outbound transport directory structure used by such 
applications as BinkleyTerm from BitBucket Software.  BinkleyTerm had an 
unusual license -- it was Public Domain and you were pretty much free to do as 
you pleased with it -- with the only caveat being that if you broke it you 
owned both halves.

[sqlite] sqlite3 file as database

[Drago, William @ CSG - NARDA-MITEQ]

Why do people use .db3 for sqlite database files? In my experience .db3 is the 
file extension for dBase III database files.

--
Bill Drago
Staff Engineer
L3 Narda-MITEQ
435 Moreland Road
Hauppauge, NY 11788
631-272-5947 / William.Drago at L-3COM.com

> -Original Message-
> From: 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
>
>
> 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 is called.
>
> Simon.
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
CONFIDENTIALITY, EXPORT CONTROL AND DISCLAIMER NOTE:This e-mail and any 
attachments are solely for the use of the addressee and may contain information 
that is privileged or confidential. Any disclosure, use or distribution of the 
information contained herein is prohibited. In the event this e-mail contains 
technical data within the definition of the International Traffic in Arms 
Regulations or Export Administration Regulations, it is subject to the export 
control laws of the U.S.Government. The recipient should check this e-mail and 
any attachments for the presence of viruses as L-3 does not accept any 
liability associated with the transmission of this e-mail. If you have received 
this communication in error, please notify the sender by reply e-mail and 
immediately delete this message and any attachments.

[sqlite] sqlite3 file as database

[Warren Young]

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 would all have implemented a 
> common metadata API, and no one would need or use extensions.

There have been many such APIs and file formats.  HFS (creator+type code), 
IPTC/EXIF/XMP/Dublin Core, EDI (balkanized into EDIFACT, X12, ODETTE?), MARC 
records (similarly balkanized), etc.

They?re all ?standards? in the XKCD sense:

  https://xkcd.com/927/

[sqlite] sqlite3 file as database

[Brian Willner]

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 the same applies to SQLite file naming conventions as well.

> Why do people use .db3 for sqlite database files? In my experience 
> .db3 is the file extension for dBase III database files.

[sqlite] sqlite3 file as database

[Warren Young]

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 and *.brd/pcb for printed circuit board 
layouts, but none of the tools agree on the format of the actual file data.  If 
you have two such apps installed, you have to make a hard choice about which 
app becomes the default to open such files, and occasionally have to fix it 
when updating the other app, as it takes over the extensions again.

This widespread unwillingness to get beyond the 8.3 limits, particularly on 
Windows, is annoying.  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.

Call your files *.myspiffyapp, or something completely unique, please.  Just 
because the data inside is managed by SQLite doesn?t mean all SQLite-based apps 
would like to open your app?s files.

[sqlite] sqlite3 file as database

[Stephen Chrzanowski]

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" --
https://en.wikipedia.org/wiki/Alphabetical_list_of_filename_extensions_%28S%E2%80%93Z%29

There are many extensions of the same .. err..
name(?)...value(?)..structure(?) that are completely different things.

Look at .DAT files.


On Mon, Sep 14, 2015 at 10:31 AM, Stephen Chrzanowski 
wrote:

> 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
> importance in a business situation.
>
> Anything I code with SQLite I do use DB3 as the file extension, simply
> because it associates that it is a database file and that it is for SQLite
> 3.  Just personal convention.  I typically mentally reserve *.SQL as text
> files, and have my compiler build resource files based on the contents of
> those text files.
>
>
> On Mon, Sep 14, 2015 at 10:07 AM, Drago, William @ CSG - NARDA-MITEQ <
> William.Drago at l-3com.com> wrote:
>
>> Why do people use .db3 for sqlite database files? In my experience .db3
>> is the file extension for dBase III database files.
>>
>> --
>> Bill Drago
>> Staff Engineer
>> L3 Narda-MITEQ
>> 435 Moreland Road
>> Hauppauge, NY 11788
>> 631-272-5947 / William.Drago at L-3COM.com
>>
>
>

[sqlite] sqlite3 file as database

[Stephen Chrzanowski]

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
importance in a business situation.

Anything I code with SQLite I do use DB3 as the file extension, simply
because it associates that it is a database file and that it is for SQLite
3.  Just personal convention.  I typically mentally reserve *.SQL as text
files, and have my compiler build resource files based on the contents of
those text files.


On Mon, Sep 14, 2015 at 10:07 AM, Drago, William @ CSG - NARDA-MITEQ <
William.Drago at l-3com.com> wrote:

> Why do people use .db3 for sqlite database files? In my experience .db3 is
> the file extension for dBase III database files.
>
> --
> Bill Drago
> Staff Engineer
> L3 Narda-MITEQ
> 435 Moreland Road
> Hauppauge, NY 11788
> 631-272-5947 / William.Drago at L-3COM.com
>

[sqlite] sqlite3 file as database

[Simon Slavin]

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 is called.

Simon.

[sqlite] sqlite3 file as database

[s.movase...@eramtec.ir]

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

[Jim Callahan]

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 separated value) data into
an SQLite table.
... Note that it is important to set the "mode" to "csv" before running the
".import" command. This is necessary to prevent the command-line shell from
trying to interpret the input file text as some other format.

sqlite> *.mode csv*
sqlite> *.import C:/work/somedata.csv tab1*

https://www.sqlite.org/cli.html

Jim

On Sat, Sep 12, 2015 at 8:19 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
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] sqlite3 file as database

[Gerry Snyder]

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
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>