Re: [sqlite] sqlite3_release_memory Question

Shawn Wilsher wrote: > That got me looking into sqlite3_release_memory. DRH would need to answer this precisely, but I believe that SQLite will free up almost all memory anyway if you have called sqlite3_close() on all open handles. Roger -

[sqlite] Re: How do I do this

Vishal Mailinglist wrote: Did not know how to do this on a database that I have in sqlite sno | id | amount 1| 1 | 200 2| 1 | 300 3 | 2 | 100 4 | 2 | 100 5 | 1 | 500 how could I subtract the sno 1 id 1 and sno 2 id 1 amount . select (select amount from tableName where sno=1 a

[sqlite] How do I do this

Hi , Did not know how to do this on a database that I have in sqlite sno | id | amount 1| 1 | 200 2| 1 | 300 3 | 2 | 100 4 | 2 | 100 5 | 1 | 500 how could I subtract the sno 1 id 1 and sno 2 id 1 amount . hope I was able to explain good . let me know if I need to explain further

Re: [sqlite] Using sqlite3 from multiple threads

You have to write the non-busy wait handlers yourself. As an example the thread that has acquired the DB and has performed its writes. At the time it commits it could post a condition variable/mutex pair. Any thread that gets a busy could simply undo its work, and wait on the condition variab

Re: [sqlite] Repository for User defined functions

The source for the SHA1 algorithm is available on the internet. On Jan 10, 2008 7:35 PM, Mike McGonagle <[EMAIL PROTECTED]> wrote: > Hello all, > I was just curious if there was a respository for user defined functions? I > was hoping to find a hash function that I could use to hash some strings >

Re: [sqlite] Optimized way of export/import of the sqlite database through C API Interface

SqliteImporter and SqliteReplicator: Command line utilities for Sqlite http://www.reddawn.net/~jsprenkl/Sqlite Source code is there to download. - To unsubscribe, send email to [EMAIL PROTECTED] --

Re: [sqlite] Using sqlite3 from multiple threads

I find it much simpler to put a mutex around the accesses (or make them a critical section). That serializes the access and avoids busy waits, retries etc. It will prevent a certain amount of read concurrency. but that may be insignificant. If you use pthreads and have plenty of reads for ea

Re: [sqlite] SQLite --> PostGres

On Fri, 11 Jan 2008 13:49:03 -0700 (MST), "Lee Crain" <[EMAIL PROTECTED]> wrote: >I mean no offense to anyone but the conversation on this subject seems a >little strange to me. > >SQLite is what it is. If it was like everything/anything else, we wouldn't >need or want it. It is designed to fill

Re: [sqlite] SQL error: database disk image is malformed

On Fri, 11 Jan 2008 15:32:28 -0500, "jose isaias cabrera" <[EMAIL PROTECTED]> wrote: > >Greetings. > >I have a problem. I have this shared DB amongst 4 co-workers where I am >getting this error: > >SQL error: database disk image is malformed > >that is after I do a, > >select * from LSOpenProjec

Re: [sqlite] Using sqlite3 from multiple threads

Am Wed, 9 Jan 2008 10:20:31 -0800 (PST) schrieb Ken: > Definately use 3.5.4. > > Not sure how to determine at compile time if the threadsafe part is > enabled. You can always compile yourself to guarantee its set, thats > what I do. > > sqlite will lock the database file for you automatically. Y

RE: [sqlite] SQLite --> PostGres

I mean no offense to anyone but the conversation on this subject seems a little strange to me. SQLite is what it is. If it was like everything/anything else, we wouldn't need or want it. It is designed to fill a particular niche in the DBMS world and from my perspective, with every passing day, i

Re: [sqlite] SQLite --> PostGres

On Fri, Jan 11, 2008 at 01:49:41PM -0600, P Kishor wrote: > > If aliases were defined for PostGres then why not for MySQL, Oracle, ^^^ ?? > > MSSQL, Firebird, VistaDB, SAP/DB, DB/2, and on and on. > Good point. Not so good. The proper question wo

[sqlite] SQL error: database disk image is malformed

Greetings. I have a problem. I have this shared DB amongst 4 co-workers where I am getting this error: SQL error: database disk image is malformed that is after I do a, select * from LSOpenProjects; and goes and display 1006 records and then I get that error above... 1006|1006|1006|NEW||

Re: [sqlite] SQLite --> PostGres

I don't think many people have your problem. I mean using Sqlite towards using PostGres. Please let's not pollute Sqlite. Thanks, Alex Katebi - Original Message From: P Kishor <[EMAIL PROTECTED]> To: sqlite-users@sqlite.org Sent: Friday, January 11, 2008 2:19:23 PM Subject: [sqlite

RE: [sqlite] SQLite --> PostGres

I like the idea of keeping SQLite strictly SQL Standard compliant. With strict compliance one has a very strong and highly transportable development platform to migrate a finished application to any SQL Standard compliant database. If all those vendor specific SQL Standard "extensions" are really

RE: [sqlite] SQLite --> PostGres

That's funny, we're currently in the process of upsizing our application from a MSSQL to SQLite. :-) Besides, I don't think it's ever good to encourage people to develop on one platform with the intent on deploying to another. I've seen people do it with Access -> MSSQL and MSSQL -> Sybase ASE

Re: [sqlite] SQLite --> PostGres

"P Kishor" <[EMAIL PROTECTED]> wrote: > I am finding that y'all (the SQLite developers) have made > many things (for example, datatypes) similar to PostGres... This is not a coincidence. I learned SQL on PostgreSQL back on '95. And I used the the PostgreSQL documentation as a guide when I was de

Re: [sqlite] SQLite --> PostGres

On 1/11/08, Samuel R. Neff <[EMAIL PROTECTED]> wrote: > > The same could be said for pretty much any other database.. they're all > similar 'cause they all follow (to some extent) the same standard. If > aliases were defined for PostGres then why not for MySQL, Oracle, MSSQL, > Firebird, VistaDB,

Re: [sqlite] SQLite --> PostGres

On 1/11/08, Rich Shepard <[EMAIL PROTECTED]> wrote: > On Fri, 11 Jan 2008, P Kishor wrote: > > > it to PostGres (pain in the tush to develop with, but great to serve > >The actual name is PostgreSQL and it's usually referred to as postgres. > > > For example, why have the "INTEGER PRIMARY KEY"

RE: [sqlite] SQLite --> PostGres

The same could be said for pretty much any other database.. they're all similar 'cause they all follow (to some extent) the same standard. If aliases were defined for PostGres then why not for MySQL, Oracle, MSSQL, Firebird, VistaDB, SAP/DB, DB/2, and on and on. I don't agree that defining alias

Re: [sqlite] SQLite --> PostGres

On Fri, 11 Jan 2008, P Kishor wrote: it to PostGres (pain in the tush to develop with, but great to serve The actual name is PostgreSQL and it's usually referred to as postgres. For example, why have the "INTEGER PRIMARY KEY" when it could just as easily be called "SERIAL"? One way migh

[sqlite] SQLite --> PostGres

I have been writing an app using SQLite (great to develop with, and to serve with to an extent), always with the intent of one day upsizing it to PostGres (pain in the tush to develop with, but great to serve with to any extent). Much to my delight, I am finding that y'all (the SQLite developers) h

Re: [sqlite] Sqlite File Access Restriction

1) Sqlite database file access restriction: Is there a built-in or preferred method to block other processes from writing or even accessing a database file when its opened first by another process. I can get this to work by having the first process to open the file issue a BEGIN Exclusion or

Re: [sqlite] updating based on JOIN

Try: update zip set city_id = ( select city_id from city where name = zip.city); HTH Ken P Kishor <[EMAIL PROTECTED]> wrote: CREATE TABLE zip (zip_code, city); CREATE TABLE city (city_id, name); INSERT a bunch of dat

[sqlite] Re: updating based on JOIN

P Kishor <[EMAIL PROTECTED]> wrote: CREATE TABLE zip (zip_code, city); CREATE TABLE city (city_id, name); INSERT a bunch of data. Then... ALTER TABLE zip ADD COLUMN city_id; UPDATE zip SET city_id = c.city_id FROM zip JOIN city c ON zip.city = c.name; UPDATE zip SET city_id = ( SELECT cit

Re: [sqlite] Proposed change to sqlite3_trace()

DRH wrote: >Legacy applications should continue to work. You might get a >compiler warning about a type mismatch on the 2nd parameter to >sqlite3_trace(). But calling a 2-parameter function with 3 >parameters is suppose to be harmless in C. Harmless in C, but not so in other languages. I ther

Re: [sqlite] Proposed change to sqlite3_trace()

Roger Binns wrote: >The biggest problem with the trace api is that there is no way to find >out what the bound parameters were. If an application follows best >practise using bound parameters all over then the trace api is rather >useless. Thanks for bringing this up again. There was a thread ab

[sqlite] updating based on JOIN

CREATE TABLE zip (zip_code, city); CREATE TABLE city (city_id, name); INSERT a bunch of data. Then... ALTER TABLE zip ADD COLUMN city_id; UPDATE zip SET city_id = c.city_id FROM zip JOIN city c ON zip.city = c.name; SQL error: near "from": syntax error hints please! -- Puneet Kishor ---

Re: [sqlite] Sqlite File Access Restriction

On Jan 9, 2008 1:12 PM, Dean Brotzel <[EMAIL PROTECTED]> wrote: > > 1) Sqlite database file access restriction: Is there a built-in or > preferred method to block other processes from writing or even accessing > a database file when its opened first by another process. I can get this > to work by

Re: [sqlite] sqlite3_release_memory Question

"Shawn Wilsher" <[EMAIL PROTECTED]> wrote: > Hmm, the documentation (http://sqlite.org/compile.html) doesn't seem > to say anything about [sqlite3_release_memory() only working if > SQLITE_ENABLE_MEMORY_MANAGEMENT=1 is used]. Is there a cost to > pay by enabling those functions, or no? > There

Re: [sqlite] sqlite3_release_memory Question

Hmm, the documentation (http://sqlite.org/compile.html) doesn't seem to say anything about that. Is there a cost to pay by enabling those functions, or no? Cheers, Shawn On Jan 11, 2008 8:42 AM, <[EMAIL PROTECTED]> wrote: > "Shawn Wilsher" <[EMAIL PROTECTED]> wrote: > > Hey all, > > > > Over i

Re: [sqlite] sqlite3_release_memory Question

"Shawn Wilsher" <[EMAIL PROTECTED]> wrote: > Hey all, > > Over in Mozilla land, we are looking for ways to free up as much > memory as possible on demand. That got me looking into > sqlite3_release_memory. However, the docs say that it tries to free > up to N bytes, but that it could free more o

[sqlite] sqlite3_release_memory Question

Hey all, Over in Mozilla land, we are looking for ways to free up as much memory as possible on demand. That got me looking into sqlite3_release_memory. However, the docs say that it tries to free up to N bytes, but that it could free more or less. My question is, how do we get it to free as mu

Re: [sqlite] Proposed change to sqlite3_trace()

[EMAIL PROTECTED] wrote: > Please follow-up with criticisms or alternative approaches > for this idea. Thanks. The biggest problem with the trace api is that there is no way to find out what the bound parameters were. If an application follows best practise using bound parameters all over then t