Re: [sqlite] Saving tables from Visual Studio designer
I'll look into this issue later today; however, the Visual Studio Designer components are not feature complete and this functionality may simply be missing. -- Joe Mistachkin ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Saving tables from Visual Studio designer
Hello I must be missing something very elementary, but for the life of me, I cannot save changes to a sqlite database from within the VS2010 designer. I started by creating a sqlite database file using Firefox SQlite Manager and adding 2 tables - user, assignments. Then, I opened the database in VS2010 designer, added a users_assignments table, added some columns to the table and added relationships to the existing tables. But I cannot save the new table and relationships back to the database. For a database newbie like me, this visual start is extremely useful. But I can't figure out what I am missing. According to the MSDN documentation, I should see a File menu item called Save : http://msdn.microsoft.com/en-us/library/41867x9f.aspx But I do not see such a menu item. Saving the .xsd file or closing the project does not change anything. Please see the following screenshot for an illustration. http://www.ismlab.usf.edu/addtable.jpg Thanks Manish ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Saving tables
Christian Smith wrote: John Stanton uttered: 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. An extension of arbitray length should be just as easy to parse as an extension up to 3 characters. "Upto" implies that the extension can also be 0, 1 or 2 characters long, so the parsing code should be sufficiently flexible to handle 0..3 characters, and by extenstion 0..n characters is not much more difficult (where n is the length of the filename). With VFAT, there is no filesystem in common use that can't handle extenstions >3 characters long. Christian My concern is being backward compatible with legacy systems or compatible with special purpose realtime OS's. An application is either portable or not, being a "little bit portable" is like being "a little bit pregnant". When in doubt use the Least Common Denominator. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
John Stanton uttered: 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. An extension of arbitray length should be just as easy to parse as an extension up to 3 characters. "Upto" implies that the extension can also be 0, 1 or 2 characters long, so the parsing code should be sufficiently flexible to handle 0..3 characters, and by extenstion 0..n characters is not much more difficult (where n is the length of the filename). With VFAT, there is no filesystem in common use that can't handle extenstions >3 characters long. Christian -- /"\ \ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL X - AGAINST MS ATTACHMENTS / \ - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
Extensions are used by such systems as MIME to indicate file type. Fitting into those conventions is better than not doing so for some capricious reason. Name extensions are easier to handle than the traditional Unix "magic" method. Trevor Talbot 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. The journal filename violates most of the same constraints, so that's not much of an argument :P - To unsubscribe, send email to [EMAIL PROTECTED] - - 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: 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] Saving tables
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. The journal filename violates most of the same constraints, so that's not much of an argument :P - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
On 11/28/06, sebcity <[EMAIL PROTECTED]> wrote: Where do you execute the SQLite program from? Is it just the sqlite.exe file? You need to start from your OS command prompt; run "sqlite3 database.filename" from there. Do not double-click sqlite3.exe. - 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] -
Re: [sqlite] Saving tables
Sqlite is admirable in the way it uses broad standards and run on just about anything which can switch electrons. It is tidy practise and simply good business to maintain that most desirable condition. 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. P Kishor wrote: > I like using .sqlite as the extension (or .sqlite3). That way no > Windows program will want to mess with it... usually 3 letter > extensions are grist for the mill > > On 11/27/06, John Stanton <[EMAIL PROTECTED]> wrote: > >> Use anything you like. Version 3 Sqlite is easy to recognize if you use >> .db3. >> >> RB Smissaert wrote: >> >>sqlite3 mydatabase.db3 >> > >> > >> > I always use the extension .db >> > What is the difference between db3 and db or maybe db2 etc.? >> > >> > RBS >> > >> > >> > -Original Message- >> > From: Kees Nuyt [mailto:[EMAIL PROTECTED] >> > Sent: 27 November 2006 22:49 >> > To: sqlite-users@sqlite.org >> > Subject: Re: [sqlite] Saving tables >> > >> > On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: >> > >> > >> >>I typed exactly what you typed there and i get >> >>SQL error: no such table: bar >> >>my command window doesnt have : "sqlite3 foo.sqlite" like yours >> > >> > >> > If you don't include a database name after the sqlite3 command, >> > sqlite uses the "memory" database, which ceases to exist after >> > you exit the program. >> > >> > So, use the following commamnd to create and open your database: >> > sqlite3 mydatabase.db3 >> > >> > and then issue the SQL commands at the prompt to create and >> > populate the table. >> > >> > Every time you want to reuse that database, you have to open it >> > in the same way: >> > sqlite3 mydatabase.db3 >> > >> > HTH >> >> >> - >> >> To unsubscribe, send email to [EMAIL PROTECTED] >> - >> >> >> > > - To unsubscribe, send email to [EMAIL PROTECTED] - - 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] -
Re: [sqlite] Saving tables
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. P Kishor wrote: > I like using .sqlite as the extension (or .sqlite3). That way no > Windows program will want to mess with it... usually 3 letter > extensions are grist for the mill > > On 11/27/06, John Stanton <[EMAIL PROTECTED]> wrote: > >> Use anything you like. Version 3 Sqlite is easy to recognize if you use >> .db3. >> >> RB Smissaert wrote: >> >>sqlite3 mydatabase.db3 >> > >> > >> > I always use the extension .db >> > What is the difference between db3 and db or maybe db2 etc.? >> > >> > RBS >> > >> > >> > -Original Message- >> > From: Kees Nuyt [mailto:[EMAIL PROTECTED] >> > Sent: 27 November 2006 22:49 >> > To: sqlite-users@sqlite.org >> > Subject: Re: [sqlite] Saving tables >> > >> > On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: >> > >> > >> >>I typed exactly what you typed there and i get >> >>SQL error: no such table: bar >> >>my command window doesnt have : "sqlite3 foo.sqlite" like yours >> > >> > >> > If you don't include a database name after the sqlite3 command, >> > sqlite uses the "memory" database, which ceases to exist after >> > you exit the program. >> > >> > So, use the following commamnd to create and open your database: >> > sqlite3 mydatabase.db3 >> > >> > and then issue the SQL commands at the prompt to create and >> > populate the table. >> > >> > Every time you want to reuse that database, you have to open it >> > in the same way: >> > sqlite3 mydatabase.db3 >> > >> > HTH >> >> >> - >> >> To unsubscribe, send email to [EMAIL PROTECTED] >> - >> >> >> > > - To unsubscribe, send email to [EMAIL PROTECTED] - -- 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] -
Re: [sqlite] Saving tables
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. In medecine the Hippocratic Oath requires "First, do no harm". Not a bad principle for IT design also. P Kishor wrote: I like using .sqlite as the extension (or .sqlite3). That way no Windows program will want to mess with it... usually 3 letter extensions are grist for the mill On 11/27/06, John Stanton <[EMAIL PROTECTED]> wrote: Use anything you like. Version 3 Sqlite is easy to recognize if you use .db3. RB Smissaert wrote: >>sqlite3 mydatabase.db3 > > > I always use the extension .db > What is the difference between db3 and db or maybe db2 etc.? > > RBS > > > -Original Message- > From: Kees Nuyt [mailto:[EMAIL PROTECTED] > Sent: 27 November 2006 22:49 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Saving tables > > On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: > > >>I typed exactly what you typed there and i get >>SQL error: no such table: bar >>my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > If you don't include a database name after the sqlite3 command, > sqlite uses the "memory" database, which ceases to exist after > you exit the program. > > So, use the following commamnd to create and open your database: > sqlite3 mydatabase.db3 > > and then issue the SQL commands at the prompt to create and > populate the table. > > Every time you want to reuse that database, you have to open it > in the same way: > sqlite3 mydatabase.db3 > > HTH - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
Where do you execute the SQLite program from? Is it just the sqlite.exe file? John Stanton wrote: > > Use anything you like. Version 3 Sqlite is easy to recognize if you use > .db3. > > RB Smissaert wrote: >>>sqlite3 mydatabase.db3 >> >> >> I always use the extension .db >> What is the difference between db3 and db or maybe db2 etc.? >> >> RBS >> >> >> -Original Message- >> From: Kees Nuyt [mailto:[EMAIL PROTECTED] >> Sent: 27 November 2006 22:49 >> To: sqlite-users@sqlite.org >> Subject: Re: [sqlite] Saving tables >> >> On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: >> >> >>>I typed exactly what you typed there and i get >>>SQL error: no such table: bar >>>my command window doesnt have : "sqlite3 foo.sqlite" like yours >> >> >> If you don't include a database name after the sqlite3 command, >> sqlite uses the "memory" database, which ceases to exist after >> you exit the program. >> >> So, use the following commamnd to create and open your database: >> sqlite3 mydatabase.db3 >> >> and then issue the SQL commands at the prompt to create and >> populate the table. >> >> Every time you want to reuse that database, you have to open it >> in the same way: >> sqlite3 mydatabase.db3 >> >> HTH > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7577236 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
Where do you execute the SQLite program from? Is it just the sqlite.exe file? P Kishor-2 wrote: > > I like using .sqlite as the extension (or .sqlite3). That way no > Windows program will want to mess with it... usually 3 letter > extensions are grist for the mill > > On 11/27/06, John Stanton <[EMAIL PROTECTED]> wrote: >> Use anything you like. Version 3 Sqlite is easy to recognize if you use >> .db3. >> >> RB Smissaert wrote: >> >>sqlite3 mydatabase.db3 >> > >> > >> > I always use the extension .db >> > What is the difference between db3 and db or maybe db2 etc.? >> > >> > RBS >> > >> > >> > -Original Message- >> > From: Kees Nuyt [mailto:[EMAIL PROTECTED] >> > Sent: 27 November 2006 22:49 >> > To: sqlite-users@sqlite.org >> > Subject: Re: [sqlite] Saving tables >> > >> > On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: >> > >> > >> >>I typed exactly what you typed there and i get >> >>SQL error: no such table: bar >> >>my command window doesnt have : "sqlite3 foo.sqlite" like yours >> > >> > >> > If you don't include a database name after the sqlite3 command, >> > sqlite uses the "memory" database, which ceases to exist after >> > you exit the program. >> > >> > So, use the following commamnd to create and open your database: >> > sqlite3 mydatabase.db3 >> > >> > and then issue the SQL commands at the prompt to create and >> > populate the table. >> > >> > Every time you want to reuse that database, you have to open it >> > in the same way: >> > sqlite3 mydatabase.db3 >> > >> > HTH >> >> >> - >> To unsubscribe, send email to [EMAIL PROTECTED] >> - >> >> > > > -- > 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] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7577190 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
Where do you execute the SQLite program from? Is it just the sqlite.exe file? Kees Nuyt wrote: > > On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: > >> >>I typed exactly what you typed there and i get >>SQL error: no such table: bar >>my command window doesnt have : "sqlite3 foo.sqlite" like yours > > If you don't include a database name after the sqlite3 command, > sqlite uses the "memory" database, which ceases to exist after > you exit the program. > > So, use the following commamnd to create and open your database: > sqlite3 mydatabase.db3 > > and then issue the SQL commands at the prompt to create and > populate the table. > > Every time you want to reuse that database, you have to open it > in the same way: > sqlite3 mydatabase.db3 > > HTH > -- > ( Kees Nuyt > ) > c[_] > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7577183 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
I like using .sqlite as the extension (or .sqlite3). That way no Windows program will want to mess with it... usually 3 letter extensions are grist for the mill On 11/27/06, John Stanton <[EMAIL PROTECTED]> wrote: Use anything you like. Version 3 Sqlite is easy to recognize if you use .db3. RB Smissaert wrote: >>sqlite3 mydatabase.db3 > > > I always use the extension .db > What is the difference between db3 and db or maybe db2 etc.? > > RBS > > > -Original Message- > From: Kees Nuyt [mailto:[EMAIL PROTECTED] > Sent: 27 November 2006 22:49 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Saving tables > > On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: > > >>I typed exactly what you typed there and i get >>SQL error: no such table: bar >>my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > If you don't include a database name after the sqlite3 command, > sqlite uses the "memory" database, which ceases to exist after > you exit the program. > > So, use the following commamnd to create and open your database: > sqlite3 mydatabase.db3 > > and then issue the SQL commands at the prompt to create and > populate the table. > > Every time you want to reuse that database, you have to open it > in the same way: > sqlite3 mydatabase.db3 > > HTH - To unsubscribe, send email to [EMAIL PROTECTED] - -- 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] -
Re: [sqlite] Saving tables
Use anything you like. Version 3 Sqlite is easy to recognize if you use .db3. RB Smissaert wrote: sqlite3 mydatabase.db3 I always use the extension .db What is the difference between db3 and db or maybe db2 etc.? RBS -Original Message- From: Kees Nuyt [mailto:[EMAIL PROTECTED] Sent: 27 November 2006 22:49 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Saving tables On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: I typed exactly what you typed there and i get SQL error: no such table: bar my command window doesnt have : "sqlite3 foo.sqlite" like yours If you don't include a database name after the sqlite3 command, sqlite uses the "memory" database, which ceases to exist after you exit the program. So, use the following commamnd to create and open your database: sqlite3 mydatabase.db3 and then issue the SQL commands at the prompt to create and populate the table. Every time you want to reuse that database, you have to open it in the same way: sqlite3 mydatabase.db3 HTH - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Saving tables
The extension doesn't actually matter. You could call it .bob for all SQLite cares. .db and .db3 are just conventions used to differentiate an SQLite 3 database from an older database. -- Eric Pankoke Founder / Lead Developer Point Of Light Software http://www.polsoftware.com/ -- Original message -- From: "RB Smissaert" <[EMAIL PROTECTED]> > > sqlite3 mydatabase.db3 > > I always use the extension .db > What is the difference between db3 and db or maybe db2 etc.? > > RBS > > > -Original Message- > From: Kees Nuyt [mailto:[EMAIL PROTECTED] > Sent: 27 November 2006 22:49 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Saving tables > > On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: > > > > >I typed exactly what you typed there and i get > >SQL error: no such table: bar > >my command window doesnt have : "sqlite3 foo.sqlite" like yours > > If you don't include a database name after the sqlite3 command, > sqlite uses the "memory" database, which ceases to exist after > you exit the program. > > So, use the following commamnd to create and open your database: > sqlite3 mydatabase.db3 > > and then issue the SQL commands at the prompt to create and > populate the table. > > Every time you want to reuse that database, you have to open it > in the same way: > sqlite3 mydatabase.db3 > > HTH > -- > ( Kees Nuyt > ) > c[_] > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > > - > > > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Saving tables
> sqlite3 mydatabase.db3 I always use the extension .db What is the difference between db3 and db or maybe db2 etc.? RBS -Original Message- From: Kees Nuyt [mailto:[EMAIL PROTECTED] Sent: 27 November 2006 22:49 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Saving tables On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: > >I typed exactly what you typed there and i get >SQL error: no such table: bar >my command window doesnt have : "sqlite3 foo.sqlite" like yours If you don't include a database name after the sqlite3 command, sqlite uses the "memory" database, which ceases to exist after you exit the program. So, use the following commamnd to create and open your database: sqlite3 mydatabase.db3 and then issue the SQL commands at the prompt to create and populate the table. Every time you want to reuse that database, you have to open it in the same way: sqlite3 mydatabase.db3 HTH -- ( Kees Nuyt ) c[_] - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Saving tables
I don't need the SQLite dll, so I take it the wrapper is of the first type. I am using the wrapper from TerraInformatica. It is called SQLiteDb.dll All the SQLite .db files I have to deal with are created by my software with the wrapper from TerraInformatica, so I take it there is no problem there. Must admit it is confusing. RBS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 27 November 2006 21:44 To: sqlite-users@sqlite.org Subject: RE: [sqlite] Saving tables It depends on how the wrapper was written. If it is a C wrapper with the SQLite code compiled in (like the SQLite COM control from NewObjects), then you are correct that all you need is the wrapper. However, if the wrapper makes calls to the DLL, then you will still need the SQLite dll along with the wrapper. Different versions of the DLL should only affect you if a function call changes or is removed. -- Eric Pankoke Founder / Lead Developer Point Of Light Software http://www.polsoftware.com/ -- Original message -- From: "RB Smissaert" <[EMAIL PROTECTED]> > Just to clear up one thing that is not 100% clear to me. > When you are using SQLite on your machine is it true that you don't need to > have anything installed if you are using a VB wrapper dll. This wrapper can > Create, update, select etc. and nil else is needed. > > Now, if I am using this wrapper and there is a new version of SQLite out > what does that mean to me? I suppose nil, unless the author of the wrapper > brings a new one out that uses features of the new version of SQLite? > > RBS > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor > Sent: 27 November 2006 20:59 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Saving tables > > SQLite is the C library that does all the db magic. You have to > somehow get to that library, which you can do from a program written > in a variety of different languages, even GUI programs, or, from > another confusingly similar named program called sqlite or sqlite > shell. Since the jump from version 2 to version 3 of SQLite, the C > library, made the data incompatible between the two versions, the > version 3 of the shell is called sqlite3 usually... it uses the SQLite > library version 3.x > > Here is what I did (my comments in-line) > > > sqlite3 foo.sqlite > > # called sqlite3 with a db named foo.sqlite > # since foo.sqlite didn't exist at first, sqlite3 helpfully created it > > > CREATE TABLE bar (a, b); > > INSERT... > > # CREATEd a table and inserted a row into it. > > > .quit > > # got out in a hurry (that was a .dot command, specific to sqlite3, the > shell) > # time passed > > > sqlite3 foo.sqlite > > # this time foo.sqlite existed, so sqlite3 just opened it up > > > SELECT * FROM bar; > > # the table bar was there, and had my data in it. > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > > > I typed exactly what you typed there and i get > > SQL error: no such table: bar > > my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > > > > > > > > > > P Kishor-2 wrote: > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> CREATE TABLE bar (a, b); > > > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > > > sqlite> .quit > > > > > > .. time passes.. > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> SELECT * FROM bar; > > > 1|my mp3 > > > sqlite> > > > > > > > > > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > >> > > >> I created a table. > > >> I populated the table. > > >> I exited SQLite. > > >> Started SQLIte again. > > >> Typed "select * from ". > > >> ANd it tells me no such table exists?? > > >> > > >> > > >> > > >> Igor Tandetnik wrote: > > >> > > > >> > sebcity <[EMAIL PROTECTED]> wrote: > > >> >> Im new to SQLite, After you create your tables how do you save them > > >> >> so they are permenently there? It might be a dumb question but i > cant > > >> >> find the answer anwhere?! > > >> > > > >> > The
Re: [sqlite] Saving tables
On Mon, 27 Nov 2006 12:43:24 -0800 (PST), you wrote: > >I typed exactly what you typed there and i get >SQL error: no such table: bar >my command window doesnt have : "sqlite3 foo.sqlite" like yours If you don't include a database name after the sqlite3 command, sqlite uses the "memory" database, which ceases to exist after you exit the program. So, use the following commamnd to create and open your database: sqlite3 mydatabase.db3 and then issue the SQL commands at the prompt to create and populate the table. Every time you want to reuse that database, you have to open it in the same way: sqlite3 mydatabase.db3 HTH -- ( Kees Nuyt ) c[_] - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
First: Dump VB and use Delphi. Second (more seriously): try to find an interface that directly exposes sqlite. Actually, you may be able to get away with this with your current wrapper: try replacing the sqlite3.dll file with a new one and see what happens. I use a Delphi unit to interface with the DLL and while I don't get any new functions, I can now use newer SQL commands through the slightly older unit. On 11/27/06, P Kishor <[EMAIL PROTECTED]> wrote: On 11/27/06, RB Smissaert <[EMAIL PROTECTED]> wrote: > Just to clear up one thing that is not 100% clear to me. > When you are using SQLite on your machine is it true that you don't need to > have anything installed if you are using a VB wrapper dll. This wrapper can > Create, update, select etc. and nil else is needed. > > Now, if I am using this wrapper and there is a new version of SQLite out > what does that mean to me? I suppose nil, unless the author of the wrapper > brings a new one out that uses features of the new version of SQLite? I don't know the first V about VB, but your logic seems immaculate. Such is the peril of using a wrapper made by someone else. I live on a similar edge with Perl DBD::SQLite which has SQLite, the library, bundled in it. If I had my druthers I would compile my own, but I lost my druthers a while back... so I suffer the consequence of laziness. Its no big deal -- in my world, DBD::SQLite is reasonably current (keep in mind, not every x.x.y release of SQLite is a crucial upgrade). You could write to the author of your VB dll, buy her a beer or something. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor > Sent: 27 November 2006 20:59 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Saving tables > > SQLite is the C library that does all the db magic. You have to > somehow get to that library, which you can do from a program written > in a variety of different languages, even GUI programs, or, from > another confusingly similar named program called sqlite or sqlite > shell. Since the jump from version 2 to version 3 of SQLite, the C > library, made the data incompatible between the two versions, the > version 3 of the shell is called sqlite3 usually... it uses the SQLite > library version 3.x > > Here is what I did (my comments in-line) > > > sqlite3 foo.sqlite > > # called sqlite3 with a db named foo.sqlite > # since foo.sqlite didn't exist at first, sqlite3 helpfully created it > > > CREATE TABLE bar (a, b); > > INSERT... > > # CREATEd a table and inserted a row into it. > > > .quit > > # got out in a hurry (that was a .dot command, specific to sqlite3, the > shell) > # time passed > > > sqlite3 foo.sqlite > > # this time foo.sqlite existed, so sqlite3 just opened it up > > > SELECT * FROM bar; > > # the table bar was there, and had my data in it. > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > > > I typed exactly what you typed there and i get > > SQL error: no such table: bar > > my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > > > > > > > > > > P Kishor-2 wrote: > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> CREATE TABLE bar (a, b); > > > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > > > sqlite> .quit > > > > > > .. time passes.. > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> SELECT * FROM bar; > > > 1|my mp3 > > > sqlite> > > > > > > > > > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > >> > > >> I created a table. > > >> I populated the table. > > >> I exited SQLite. > > >> Started SQLIte again. > > >> Typed "select * from ". > > >> ANd it tells me no such table exists?? > > >> > > >> > > >> > > >> Igor Tandetnik wrote: > > >> > > > >> > sebcity <[EMAIL PROTECTED]> wrote: > > >> >> Im new to SQLite, After you create your tables how do you save them > > >> >> so they are permenently there? It might be a dumb question but i > cant > > >> >> find the answer anwhere?! > > >> > > > >> > They are "permanently there" from the very moment you create them. > All > > >> > changes are written to the database
RE: [sqlite] Saving tables
It depends on how the wrapper was written. If it is a C wrapper with the SQLite code compiled in (like the SQLite COM control from NewObjects), then you are correct that all you need is the wrapper. However, if the wrapper makes calls to the DLL, then you will still need the SQLite dll along with the wrapper. Different versions of the DLL should only affect you if a function call changes or is removed. -- Eric Pankoke Founder / Lead Developer Point Of Light Software http://www.polsoftware.com/ -- Original message -- From: "RB Smissaert" <[EMAIL PROTECTED]> > Just to clear up one thing that is not 100% clear to me. > When you are using SQLite on your machine is it true that you don't need to > have anything installed if you are using a VB wrapper dll. This wrapper can > Create, update, select etc. and nil else is needed. > > Now, if I am using this wrapper and there is a new version of SQLite out > what does that mean to me? I suppose nil, unless the author of the wrapper > brings a new one out that uses features of the new version of SQLite? > > RBS > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor > Sent: 27 November 2006 20:59 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Saving tables > > SQLite is the C library that does all the db magic. You have to > somehow get to that library, which you can do from a program written > in a variety of different languages, even GUI programs, or, from > another confusingly similar named program called sqlite or sqlite > shell. Since the jump from version 2 to version 3 of SQLite, the C > library, made the data incompatible between the two versions, the > version 3 of the shell is called sqlite3 usually... it uses the SQLite > library version 3.x > > Here is what I did (my comments in-line) > > > sqlite3 foo.sqlite > > # called sqlite3 with a db named foo.sqlite > # since foo.sqlite didn't exist at first, sqlite3 helpfully created it > > > CREATE TABLE bar (a, b); > > INSERT... > > # CREATEd a table and inserted a row into it. > > > .quit > > # got out in a hurry (that was a .dot command, specific to sqlite3, the > shell) > # time passed > > > sqlite3 foo.sqlite > > # this time foo.sqlite existed, so sqlite3 just opened it up > > > SELECT * FROM bar; > > # the table bar was there, and had my data in it. > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > > > I typed exactly what you typed there and i get > > SQL error: no such table: bar > > my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > > > > > > > > > > P Kishor-2 wrote: > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> CREATE TABLE bar (a, b); > > > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > > > sqlite> .quit > > > > > > .. time passes.. > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> SELECT * FROM bar; > > > 1|my mp3 > > > sqlite> > > > > > > > > > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > >> > > >> I created a table. > > >> I populated the table. > > >> I exited SQLite. > > >> Started SQLIte again. > > >> Typed "select * from ". > > >> ANd it tells me no such table exists?? > > >> > > >> > > >> > > >> Igor Tandetnik wrote: > > >> > > > >> > sebcity <[EMAIL PROTECTED]> wrote: > > >> >> Im new to SQLite, After you create your tables how do you save them > > >> >> so they are permenently there? It might be a dumb question but i > cant > > >> >> find the answer anwhere?! > > >> > > > >> > They are "permanently there" from the very moment you create them. > All > > >> > changes are written to the database file when a transaction is > > >> > committed, or at the end of every statement if you don't open any > > >> > transactions explicitly. > > >> > > > >> > Igor Tandetnik > > >> > > > >> > > > >> > > > >> > ---
Re: [sqlite] Saving tables
On 11/27/06, RB Smissaert <[EMAIL PROTECTED]> wrote: Just to clear up one thing that is not 100% clear to me. When you are using SQLite on your machine is it true that you don't need to have anything installed if you are using a VB wrapper dll. This wrapper can Create, update, select etc. and nil else is needed. Now, if I am using this wrapper and there is a new version of SQLite out what does that mean to me? I suppose nil, unless the author of the wrapper brings a new one out that uses features of the new version of SQLite? I don't know the first V about VB, but your logic seems immaculate. Such is the peril of using a wrapper made by someone else. I live on a similar edge with Perl DBD::SQLite which has SQLite, the library, bundled in it. If I had my druthers I would compile my own, but I lost my druthers a while back... so I suffer the consequence of laziness. Its no big deal -- in my world, DBD::SQLite is reasonably current (keep in mind, not every x.x.y release of SQLite is a crucial upgrade). You could write to the author of your VB dll, buy her a beer or something. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor Sent: 27 November 2006 20:59 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Saving tables SQLite is the C library that does all the db magic. You have to somehow get to that library, which you can do from a program written in a variety of different languages, even GUI programs, or, from another confusingly similar named program called sqlite or sqlite shell. Since the jump from version 2 to version 3 of SQLite, the C library, made the data incompatible between the two versions, the version 3 of the shell is called sqlite3 usually... it uses the SQLite library version 3.x Here is what I did (my comments in-line) > sqlite3 foo.sqlite # called sqlite3 with a db named foo.sqlite # since foo.sqlite didn't exist at first, sqlite3 helpfully created it > CREATE TABLE bar (a, b); > INSERT... # CREATEd a table and inserted a row into it. > .quit # got out in a hurry (that was a .dot command, specific to sqlite3, the shell) # time passed > sqlite3 foo.sqlite # this time foo.sqlite existed, so sqlite3 just opened it up > SELECT * FROM bar; # the table bar was there, and had my data in it. On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > I typed exactly what you typed there and i get > SQL error: no such table: bar > my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > > > > P Kishor-2 wrote: > > > >>sqlite3 foo.sqlite > > SQLite version 3.3.7 > > Enter ".help" for instructions > > sqlite> CREATE TABLE bar (a, b); > > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > > sqlite> .quit > > > > .. time passes.. > > > >>sqlite3 foo.sqlite > > SQLite version 3.3.7 > > Enter ".help" for instructions > > sqlite> SELECT * FROM bar; > > 1|my mp3 > > sqlite> > > > > > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > >> > >> I created a table. > >> I populated the table. > >> I exited SQLite. > >> Started SQLIte again. > >> Typed "select * from ". > >> ANd it tells me no such table exists?? > >> > >> > >> > >> Igor Tandetnik wrote: > >> > > >> > sebcity <[EMAIL PROTECTED]> wrote: > >> >> Im new to SQLite, After you create your tables how do you save them > >> >> so they are permenently there? It might be a dumb question but i cant > >> >> find the answer anwhere?! > >> > > >> > They are "permanently there" from the very moment you create them. All > >> > changes are written to the database file when a transaction is > >> > committed, or at the end of every statement if you don't open any > >> > transactions explicitly. > >> > > >> > Igor Tandetnik > >> > -- 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] -
RE: [sqlite] Saving tables
Just to clear up one thing that is not 100% clear to me. When you are using SQLite on your machine is it true that you don't need to have anything installed if you are using a VB wrapper dll. This wrapper can Create, update, select etc. and nil else is needed. Now, if I am using this wrapper and there is a new version of SQLite out what does that mean to me? I suppose nil, unless the author of the wrapper brings a new one out that uses features of the new version of SQLite? RBS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor Sent: 27 November 2006 20:59 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Saving tables SQLite is the C library that does all the db magic. You have to somehow get to that library, which you can do from a program written in a variety of different languages, even GUI programs, or, from another confusingly similar named program called sqlite or sqlite shell. Since the jump from version 2 to version 3 of SQLite, the C library, made the data incompatible between the two versions, the version 3 of the shell is called sqlite3 usually... it uses the SQLite library version 3.x Here is what I did (my comments in-line) > sqlite3 foo.sqlite # called sqlite3 with a db named foo.sqlite # since foo.sqlite didn't exist at first, sqlite3 helpfully created it > CREATE TABLE bar (a, b); > INSERT... # CREATEd a table and inserted a row into it. > .quit # got out in a hurry (that was a .dot command, specific to sqlite3, the shell) # time passed > sqlite3 foo.sqlite # this time foo.sqlite existed, so sqlite3 just opened it up > SELECT * FROM bar; # the table bar was there, and had my data in it. On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > I typed exactly what you typed there and i get > SQL error: no such table: bar > my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > > > > P Kishor-2 wrote: > > > >>sqlite3 foo.sqlite > > SQLite version 3.3.7 > > Enter ".help" for instructions > > sqlite> CREATE TABLE bar (a, b); > > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > > sqlite> .quit > > > > .. time passes.. > > > >>sqlite3 foo.sqlite > > SQLite version 3.3.7 > > Enter ".help" for instructions > > sqlite> SELECT * FROM bar; > > 1|my mp3 > > sqlite> > > > > > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > >> > >> I created a table. > >> I populated the table. > >> I exited SQLite. > >> Started SQLIte again. > >> Typed "select * from ". > >> ANd it tells me no such table exists?? > >> > >> > >> > >> Igor Tandetnik wrote: > >> > > >> > sebcity <[EMAIL PROTECTED]> wrote: > >> >> Im new to SQLite, After you create your tables how do you save them > >> >> so they are permenently there? It might be a dumb question but i cant > >> >> find the answer anwhere?! > >> > > >> > They are "permanently there" from the very moment you create them. All > >> > changes are written to the database file when a transaction is > >> > committed, or at the end of every statement if you don't open any > >> > transactions explicitly. > >> > > >> > Igor Tandetnik > >> > > >> > > >> > > >> - > >> > To unsubscribe, send email to [EMAIL PROTECTED] > >> > > >> - > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 > >> Sent from the SQLite mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, send email to [EMAIL PROTECTED] > >> - > >> > >> > > > > > > -- > > 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 > >
Re: [sqlite] Saving tables
Can you describe in more detail the process you're trying to use to do this? -- Eric Pankoke Founder / Lead Developer Point Of Light Software http://www.polsoftware.com/ -- Original message -- From: sebcity <[EMAIL PROTECTED]> > > Nope, how would i do that? > > Eric Pankoke wrote: > > > > Did you open the database when you launched SQLite again? Sorry if this > > is a stupid question, but I've never used SQLite from a command line or > > the shell. > > > > -- > > Eric Pankoke > > Founder / Lead Developer > > Point Of Light Software > > http://www.polsoftware.com/ > > > > -- Original message -- > > From: sebcity <[EMAIL PROTECTED]> > >> > >> I created a table. > >> I populated the table. > >> I exited SQLite. > >> Started SQLIte again. > >> Typed "select * from ". > >> ANd it tells me no such table exists?? > >> > >> > >> > >> Igor Tandetnik wrote: > >> > > >> > sebcity <[EMAIL PROTECTED]> wrote: > >> >> Im new to SQLite, After you create your tables how do you save them > >> >> so they are permenently there? It might be a dumb question but i cant > >> >> find the answer anwhere?! > >> > > >> > They are "permanently there" from the very moment you create them. All > >> > changes are written to the database file when a transaction is > >> > committed, or at the end of every statement if you don't open any > >> > transactions explicitly. > >> > > >> > Igor Tandetnik > >> > > >> > > >> > > >> - > >> > To unsubscribe, send email to [EMAIL PROTECTED] > >> > > >> - > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 > >> Sent from the SQLite mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, send email to [EMAIL PROTECTED] > >> - > >> > > > > > > - > > To unsubscribe, send email to [EMAIL PROTECTED] > > - > > > > > > > > -- > View this message in context: > http://www.nabble.com/Saving-tables-tf2714011.html#a7567686 > Sent from the SQLite mailing list archive at Nabble.com. > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
SQLite is the C library that does all the db magic. You have to somehow get to that library, which you can do from a program written in a variety of different languages, even GUI programs, or, from another confusingly similar named program called sqlite or sqlite shell. Since the jump from version 2 to version 3 of SQLite, the C library, made the data incompatible between the two versions, the version 3 of the shell is called sqlite3 usually... it uses the SQLite library version 3.x Here is what I did (my comments in-line) sqlite3 foo.sqlite # called sqlite3 with a db named foo.sqlite # since foo.sqlite didn't exist at first, sqlite3 helpfully created it CREATE TABLE bar (a, b); INSERT... # CREATEd a table and inserted a row into it. .quit # got out in a hurry (that was a .dot command, specific to sqlite3, the shell) # time passed sqlite3 foo.sqlite # this time foo.sqlite existed, so sqlite3 just opened it up SELECT * FROM bar; # the table bar was there, and had my data in it. On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: I typed exactly what you typed there and i get SQL error: no such table: bar my command window doesnt have : "sqlite3 foo.sqlite" like yours P Kishor-2 wrote: > >>sqlite3 foo.sqlite > SQLite version 3.3.7 > Enter ".help" for instructions > sqlite> CREATE TABLE bar (a, b); > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > sqlite> .quit > > .. time passes.. > >>sqlite3 foo.sqlite > SQLite version 3.3.7 > Enter ".help" for instructions > sqlite> SELECT * FROM bar; > 1|my mp3 > sqlite> > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: >> >> I created a table. >> I populated the table. >> I exited SQLite. >> Started SQLIte again. >> Typed "select * from ". >> ANd it tells me no such table exists?? >> >> >> >> Igor Tandetnik wrote: >> > >> > sebcity <[EMAIL PROTECTED]> wrote: >> >> Im new to SQLite, After you create your tables how do you save them >> >> so they are permenently there? It might be a dumb question but i cant >> >> find the answer anwhere?! >> > >> > They are "permanently there" from the very moment you create them. All >> > changes are written to the database file when a transaction is >> > committed, or at the end of every statement if you don't open any >> > transactions explicitly. >> > >> > Igor Tandetnik >> > >> > >> > >> - >> > To unsubscribe, send email to [EMAIL PROTECTED] >> > >> - >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 >> Sent from the SQLite mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, send email to [EMAIL PROTECTED] >> - >> >> > > > -- > 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] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7567649 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] - -- 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] -
Re: [sqlite] Saving tables
If you are using Sqlite3 to access the DB you would -0 sqlite3 harry.db3 //Creates a database called harry.db3 enter some SQL to create a table and populate it exit To retrieve your data sqlite3 harry.db3//Opens DB harry.db3 enter some SQL e.g. SELECT * FROM mytab; you will get the contents of the table. exit The DB harry.db3 will be a file called harry.db3 in your current working directory. sebcity wrote: I created a table. I populated the table. I exited SQLite. Started SQLIte again. Typed "select * from ". ANd it tells me no such table exists?? Igor Tandetnik wrote: sebcity <[EMAIL PROTECTED]> wrote: Im new to SQLite, After you create your tables how do you save them so they are permenently there? It might be a dumb question but i cant find the answer anwhere?! They are "permanently there" from the very moment you create them. All changes are written to the database file when a transaction is committed, or at the end of every statement if you don't open any transactions explicitly. Igor Tandetnik - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
Nope, how would i do that? Eric Pankoke wrote: > > Did you open the database when you launched SQLite again? Sorry if this > is a stupid question, but I've never used SQLite from a command line or > the shell. > > -- > Eric Pankoke > Founder / Lead Developer > Point Of Light Software > http://www.polsoftware.com/ > > -- Original message -- > From: sebcity <[EMAIL PROTECTED]> >> >> I created a table. >> I populated the table. >> I exited SQLite. >> Started SQLIte again. >> Typed "select * from ". >> ANd it tells me no such table exists?? >> >> >> >> Igor Tandetnik wrote: >> > >> > sebcity <[EMAIL PROTECTED]> wrote: >> >> Im new to SQLite, After you create your tables how do you save them >> >> so they are permenently there? It might be a dumb question but i cant >> >> find the answer anwhere?! >> > >> > They are "permanently there" from the very moment you create them. All >> > changes are written to the database file when a transaction is >> > committed, or at the end of every statement if you don't open any >> > transactions explicitly. >> > >> > Igor Tandetnik >> > >> > >> > >> - >> > To unsubscribe, send email to [EMAIL PROTECTED] >> > >> - >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 >> Sent from the SQLite mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, send email to [EMAIL PROTECTED] >> - >> > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7567686 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
I typed exactly what you typed there and i get SQL error: no such table: bar my command window doesnt have : "sqlite3 foo.sqlite" like yours P Kishor-2 wrote: > >>sqlite3 foo.sqlite > SQLite version 3.3.7 > Enter ".help" for instructions > sqlite> CREATE TABLE bar (a, b); > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > sqlite> .quit > > .. time passes.. > >>sqlite3 foo.sqlite > SQLite version 3.3.7 > Enter ".help" for instructions > sqlite> SELECT * FROM bar; > 1|my mp3 > sqlite> > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: >> >> I created a table. >> I populated the table. >> I exited SQLite. >> Started SQLIte again. >> Typed "select * from ". >> ANd it tells me no such table exists?? >> >> >> >> Igor Tandetnik wrote: >> > >> > sebcity <[EMAIL PROTECTED]> wrote: >> >> Im new to SQLite, After you create your tables how do you save them >> >> so they are permenently there? It might be a dumb question but i cant >> >> find the answer anwhere?! >> > >> > They are "permanently there" from the very moment you create them. All >> > changes are written to the database file when a transaction is >> > committed, or at the end of every statement if you don't open any >> > transactions explicitly. >> > >> > Igor Tandetnik >> > >> > >> > >> - >> > To unsubscribe, send email to [EMAIL PROTECTED] >> > >> - >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 >> Sent from the SQLite mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, send email to [EMAIL PROTECTED] >> - >> >> > > > -- > 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] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7567649 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
Did you open the database when you launched SQLite again? Sorry if this is a stupid question, but I've never used SQLite from a command line or the shell. -- Eric Pankoke Founder / Lead Developer Point Of Light Software http://www.polsoftware.com/ -- Original message -- From: sebcity <[EMAIL PROTECTED]> > > I created a table. > I populated the table. > I exited SQLite. > Started SQLIte again. > Typed "select * from ". > ANd it tells me no such table exists?? > > > > Igor Tandetnik wrote: > > > > sebcity <[EMAIL PROTECTED]> wrote: > >> Im new to SQLite, After you create your tables how do you save them > >> so they are permenently there? It might be a dumb question but i cant > >> find the answer anwhere?! > > > > They are "permanently there" from the very moment you create them. All > > changes are written to the database file when a transaction is > > committed, or at the end of every statement if you don't open any > > transactions explicitly. > > > > Igor Tandetnik > > > > > > - > > To unsubscribe, send email to [EMAIL PROTECTED] > > - > > > > > > > > -- > View this message in context: > http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 > Sent from the SQLite mailing list archive at Nabble.com. > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Saving tables
sqlite3 foo.sqlite SQLite version 3.3.7 Enter ".help" for instructions sqlite> CREATE TABLE bar (a, b); sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); sqlite> .quit .. time passes.. sqlite3 foo.sqlite SQLite version 3.3.7 Enter ".help" for instructions sqlite> SELECT * FROM bar; 1|my mp3 sqlite> On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: I created a table. I populated the table. I exited SQLite. Started SQLIte again. Typed "select * from ". ANd it tells me no such table exists?? Igor Tandetnik wrote: > > sebcity <[EMAIL PROTECTED]> wrote: >> Im new to SQLite, After you create your tables how do you save them >> so they are permenently there? It might be a dumb question but i cant >> find the answer anwhere?! > > They are "permanently there" from the very moment you create them. All > changes are written to the database file when a transaction is > committed, or at the end of every statement if you don't open any > transactions explicitly. > > Igor Tandetnik > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] - -- 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] -
Re: [sqlite] Saving tables
I created a table. I populated the table. I exited SQLite. Started SQLIte again. Typed "select * from ". ANd it tells me no such table exists?? Igor Tandetnik wrote: > > sebcity <[EMAIL PROTECTED]> wrote: >> Im new to SQLite, After you create your tables how do you save them >> so they are permenently there? It might be a dumb question but i cant >> find the answer anwhere?! > > They are "permanently there" from the very moment you create them. All > changes are written to the database file when a transaction is > committed, or at the end of every statement if you don't open any > transactions explicitly. > > Igor Tandetnik > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > > > -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7567183 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] Saving tables
Hi, Im new to SQLite, After you create your tables how do you save them so they are permenently there? It might be a dumb question but i cant find the answer anwhere?! -- View this message in context: http://www.nabble.com/Saving-tables-tf2714011.html#a7566646 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
