Re: [sqlite] SQLite turns 10 years old

Happy birthday and thanks for the memories. This has been a damn nice project. On Sat, May 29, 2010 at 6:57 AM, D. Richard Hipp wrote: > The first code check-in for SQLite occurred on 2000-05-29 14:26 UTC - > ten years ago today. > >    

[sqlite] Insert Using Tcl Array?

If SQLite can return to me a Tcl array from SELECT, why does the feature not exist to INSERT, UPDATE, or DELETE using a properly formed Tcl array as an argument? Seems nice to have, but perhaps I'm not aware of possible dangers in such a feature. Thanks. -- Ross

Re: [sqlite] WAL in SQLite

On Sat, May 29, 2010 at 9:19 PM, Roger Binns wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 05/29/2010 02:01 PM, Richard Hipp wrote: > > Does anybody know if mmap() works for network files? > > It does. However there is no way to ensure that everyone

Re: [sqlite] WAL in SQLite

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/29/2010 02:01 PM, Richard Hipp wrote: > Does anybody know if mmap() works for network files? It does. However there is no way to ensure that everyone seeing the file will have a consistent view of it. This is especially the case when they

Re: [sqlite] WAL in SQLite

Richard, thank you for responding to my questions about SQLite's WAL design. Richard Hipp wrote: > We've been working on an incremental checkpointing mechanism for about a > week. With incremental checkpointing, the checkpoint can be run more or > less continuously in a background thread or

Re: [sqlite] WAL in SQLite

On Sat, May 29, 2010 at 3:49 PM, Darren Duncan wrote: > > 2. Quoth the raven: > > "The wal-index greatly improves the performance of readers, but the use > of > shared memory means that all readers must exist on the same machine. This > is > why the write-ahead log

Re: [sqlite] SQLite turns 10 years old

> Thanks, everybody, for helping to make SQLite the most widely deployed > SQL database engine in the world. And Happy 10th Birthday to SQLite! No, *WE* have to thank *YOU* for this great piece of work, that you give to use for free! Amazing! Thank you! bye, Michael

[sqlite] WAL in SQLite

In regards to WAL (write-ahead-logging) support being added to SQLite for version 3.7.0, I have a few comments, questions, suggestions, etc. Most of them refer to parts of http://www.sqlite.org/draft/wal.html . 1. Congratulations on this move, which should greatly improve SQLite's utility

Re: [sqlite] SQLite turns 10 years old

Congratulations on this milestone. I also just realized now that you're adding WAL to SQLite; I have more to say on this, but that will be in a new thread. -- Darren Duncan D. Richard Hipp wrote: > The first code check-in for SQLite occurred on 2000-05-29 14:26 UTC - > ten years ago today.

Re: [sqlite] UTC/GMT conversion back and forth

On Fri, 28 May 2010 20:12:54 +0300 Andrejs Igumenovs wrote: Finally! A question that I can answer. For all practical (and most impractical) (Drum roll) UTC = GMT, or alternatively, GMT = UTC UTC is Coordinated Universal Time, which one would think would be

[sqlite] TEA not latest version?

Congratulations on the 10th birthday. On: http://www.sqlite.org/download.html The TEA download link is version 3_6_23, whereas everything else is 3.6.23.1. >From what I understand from the release notes, the changes from 3.6.23 to 3.6.23.1 affect the TEA version too. How do I get to the

Re: [sqlite] SQLite turns 10 years old

Mr. D. Richard Hipp, 10-year anniversary a great news and real pleasure to see how your and supporters' skills turn this library into such big power. Sometimes it makes me sad I can't explain to a non-developer what is so great about sqlite, what makes it appearing in so many software packages.

Re: [sqlite] SQLITE_OMIT_WSD (3.6.23.1)

On May 29, 2010, at 10:19 AM, Albert Kim wrote: > > Hi Dan, > It doesn't matter that it will never be written to. Since the > variable is a > non-const static it will get mapped into the WSD portion of memory. Is a problem in practice? Or just messy?

[sqlite] SQLite turns 10 years old

The first code check-in for SQLite occurred on 2000-05-29 14:26 UTC - ten years ago today. http://www.sqlite.org/src/timeline?c=2000-05-29+14:26 Some of the code in SQLite (such as the Lemon parser generator and the printf implementation) dates back to the late 1980s. But the core of

Re: [sqlite] Getting a "rowid" from a view

On Fri, 28 May 2010 17:19:37 -0700, Jim Terman wrote: >SELECT rowid FROM phonebook > where last_name = "Smith" > and first_name = "John"; By the way, string literals (text) in SQL should be delimited by single quotes, not double quotes. Double quotes are used to allow

Re: [sqlite] Getting a "rowid" from a view

On Sat, 29 May 2010 02:35:22 +0100, Simon Slavin wrote: >On 29 May 2010, at 2:30am, Jim Terman wrote: > >> I want the 'rowid' of the view. In other words I'd like to now what row >> John Smith is in the view. I can do it with a view that is ordered by >> using count(*),

Re: [sqlite] Getting a "rowid" from a view

On Fri, 28 May 2010 17:19:37 -0700, Jim Terman wrote: >Say I have a table of phone numbers > >CREATE TABLE phonebook (first_name TEXT, last_name TEXT, phone_number TEXT); > >I want to sort this by name, so I create a view > >CREATE VIEW phonebook_order AS SELECT first_name,

Re: [sqlite] UTC/GMT conversion back and forth

sqlite> create table t (d integer); sqlite> insert into t values (datetime('now')); sqlite> select * from t; 2010-05-29 11:19:20 << you'll note this should be in GMT sqlite> select datetime(d,'localtime') from t; 2010-05-29 06:19:20 You can, of course, get your time in whatever format you

[sqlite] UTC/GMT conversion back and forth

Hi, I've got dates and times stored in GMT. When I perform my calculations using date() function for ex., i need to use those dates and times normalized to the current location I'm now in (this is variable). This thing makes me lost a bit of how to implement.. Any ideas ? Thanks!

Re: [sqlite] No conflict clause in foreign key clause?

On May 28, 2010, at 10:54 PM, Robert Nickel wrote: > I notice that the foreign key clause > (http://www.sqlite.org/syntaxdiagrams.html#foreign-key-clause) does > not > include a conflict clause > (http://www.sqlite.org/syntaxdiagrams.html#conflict-clause). I always > specify "ON CONFLICT