#x27;-11-24 12:00:00');
1721388.0
sqlite> Select julianday('0001-11-24 12:00:00');
1721753.0
There is no year 0. The calendar goes from -1 BCE to 1 CE. -11-24
is 1 BCE. So, if you want November 24, 4714 B.C. you need to say
sqlite> Sel
comments about timeBeginPeriod() in
http://www.geisswerks.com/ryan/FAQS/timing.html
http://blogs.msdn.com/larryosterman/archive/2005/09/08/462477.aspx
or google "timeBeginPeriod"
e
--
Doug Currie
Londonderry, NH, USA
---
were first published in 1974 by Don Chamberlin and Ray
Boyce at the ACM–SIGFIDET Workshop on Data Description, whereas "ess
cue ell" is used for subsequent standardized versions of the language.
e
--
Doug Currie
Londonderry, NH, USA
--
occur when multiple threads are waiting on the event;
they all wake up and compete for the resource again. For better
solutions, see: http://world.std.com/~jmhart/batons.htm
e
--
Doug Currie
Londonderry, NH, USA
-
To un
events.
Of course, if you expect there to be intervals when there are no
waiting threads, and you can afford to wait for that interval for a
synchronization point, and you don't care the order in which the
inserts are performed, the Automatic Reset event might work.
e
> On 6/1/07, Do
eless, there are ways to print floating point numbers
readably. http://portal.acm.org/citation.cfm?id=93559
e
--
Doug Currie
Londonderry, NH, USA
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
f digits necessary to reconstruct the number. This will be the
number of digits that Serena expects.
e
--
Doug Currie
Londonderry, NH, USA
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
piled with gcc, but I don't know what version.
However, if I compile from sources, I get
C:\Dev\sqlite\sqlite-3.4.2\bld>.\sqlite3
SQLite version 3.4.2
Enter ".help" for instructions
sqlite> select round(98926650.5, 1);
98926650.5
I
unctions, and so
results between Microsoft Visual C++ compiled and gcc compiled
versions of sqlite3 are bound to produce different results.
Why my gcc 3.4.5 compiled sqlite3.exe and the one from the sqlite.org
downloads page produce different results is still a mystery to me.
e
--
Doug Cur
g and
double; that's why I keep harping on Steele and White's (and
Clinger's) PLDI 1990 papers. What I don't know is why this bug appears
in the binary from sqlite.org but not in the version I build myself
with gcc 3.4.5 from SQLite version 3.4
On Wednesday, September 05, 2007 Arjen Markus wrote:
> Doug Currie wrote:
>>I suspect the bug is in the functions that convert between string and
>>double; that's why I keep harping on Steele and White's (and
>>Clinger's) PLDI 1990 papers. What I don
issa) whereas gcc uses 96 bits (64 bit mantissa). Note that
realvalue above is declared as LONGDOUBLE_TYPE (long double).
http://msdn2.microsoft.com/en-us/library/9c3yd98k(VS.80).aspx
http://msdn2.microsoft.com/en-us/library/9cx8xs15(vs.80).aspx
e
--
Doug Currie
Londonderry, NH, USA
--
On May 15, 2009, at 9:07 AM, Sam Carleton wrote:
> I would like CURRENT_TIMESTAMP to be more accurate than just one
> second, any suggestions on how I might do that once? My solution is
> all a C/C++ interface, so all features are open to me.
Option 1 - use: julianday('now') instead of CURR
On May 18, 2009, at 5:32 PM, Allen Fowler wrote:
>>> The simple solution would just create a race condition... i think:
>>>
>>> 1) INSERT INTO status_table FROM SELECT oldest task in queue
>>> 2) DELETE oldest task in queue
>>>
>>> Right?
>>
>> It might work fine if you wrap it in an exclusive
>>
On May 19, 2009, at 10:05 AM, Jean-Denis Muys wrote:
> On 5/19/09 2:44 PM, "Igor Tandetnik" wrote:
>>
>> Wikipedia gives a definition different from yours, for what it's
>> worth:
>>
>> http://en.wikipedia.org/wiki/Remainder#The_case_of_general_integers
>
> Also to support my version, the same
On Jun 12, 2009, at 3:46 PM, Allen Fowler wrote:
> sqlite>
> select *, min((strftime('%s', end) - strftime('%s', start))) as
> length
> from
> ...> events where
> ...> start < datetime('now', '+1 day','start of day',
> '+9 hours','+30 minutes')
> ...> and end > datetime('now', '+1 day','
On Jul 7, 2009, at 4:36 PM, nixonron wrote:
> conn = sqlite3.connect('c:\Ujimadata\aid.sqlite')
Perhaps you meant
conn = sqlite3.connect('c:\\Ujimadata\\aid.sqlite')
or
conn = sqlite3.connect('c:/Ujimadata/aid.sqlite')
e
___
sqlite-users mailing l
On Jul 24, 2009, at 8:44 AM, D. Richard Hipp wrote:
> SQLite database files are cross-platform. All you have to do is copy
> the file to the new machine. There is no separate "external format".
> The same database file format work on all platforms.
Just make sure that if you are moving to a new
On Jul 27, 2009, at 10:33 AM, CityDev wrote:
> It's true that Codd and Date used the term 'relational' (They
> championed the
> N-ary Relational Model - others were around at the same time) but
> it's not
> easy to track the origin of the term in mathematics.
http://en.wikipedia.org/wiki/Rel
On Aug 23, 2009, at 6:46 AM, Chris Dew wrote:
> Note: this is not for production code, just an experiment in keeping a
> history of application 'state', allowing current state to be
> recalculated if an historic input is received 'late'. See
> http://www.finalcog.com/haskell-decoupling-time-from
On Oct 30, 2009, at 10:14 AM, P Kishor wrote:
> Actually, there can be one bad effect of Darren's suggestion, now that
> I think of it, and that would be for those who don't care for strong
> typing. They will end up getting strong typing for all non-UNIVERSAL
> columns whether they like it or no
On Nov 5, 2009, at 5:15 PM, Beau Wilkinson wrote:
> I really think this warrants further discussion. Perhaps the correct
> answer (that ARMs implement a non-standard FP type which is
> incompatible with Sqlite) is already out there, but I think the
> issues I raised with that answer should
e pad character is a
> .
So, using this terminology, the SQLite default collating sequence has
the NO PAD attribute, and the pad character is NUL.
Jeff, can you solve your problem with a custom collating sequence?
e
--
Doug Currie
Londonderry, NH, USA
---
+1
> This mailing-list business is becoming a royal pain in the derriere.
> Every other mailing list behaves differently... some default to the
> list, others to the OP. Why can't we all get along.
> Please set the list so default reply is to the list.
http:/
he reason an import library isn't included is because you need a
> different one for each compiler you use to link.
Right, and with gcc on Windows (mingw/msys or cygwin), you don't need
an import library at all; gcc will link against the DLL it
Thursday, May 4, 2006, 1:27:49 PM, Dennis Cote wrote:
> More mysteries. To investigate this low insert performance under WinXP I
> wrote a simple test program that loops writing one character to a file
> and then flushing the file. The strange thing is that it seems to
> alternate between two dif
p=BlueSky the shadow pager.
> Note, I'm not suggesting that you should implement anything like this
> in SQLite...
Me neither. ;-)
e
--
Doug Currie
Londonderry, NH
Monday, September 25, 2006, 1:46:12 PM, David Champagne wrote:
> and then I execute a query
> SELECT * FROM License WHERE FORM = "form";
> I get all rows returned
Try:
SELECT * FROM License WHERE FORM = 'form';
e
--
n-posix systems.
>>
>> One can register a Ctrl-C handler on Windows with SetConsoleCtrlHandler.
>> But the handler is invoked on a background thread created by the system
>> specifically for this purpose, so sqlite3_interrupt couldn't be used
>> there, either.
>>
>> Igor Tandetnik
--
Doug Currie
Londonderry, NH
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
---
-8<----- End of Original message text --
--
Doug Currie
Londonderry, NH, USA
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
here is hardly ever a reason to do this
since gcc will link against the DLL directly.
e
--
Doug Currie
Londonderry, NH, USA
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
On Aug 10, 2008, at 2:12 PM, CAVALO SCHMIDT wrote:
> salutations, using VC++ in WinXP.
>
> I would like to know if it's possible to import and use the
> sqlite3.dll file and/or the sqlite database file as a resource in a
> C++ project, so that it will be integrated to the final Win32
> executable
On Nov 12, 2008, at 10:31 PM, henry wrote:
> my app, I opened a database handler, insert some records, delete some
> records, then closed the database handler. The problem is the next
> time
> when I connect the Sqlite, the actions I did last time has all gone
> away, it did not take any effect
On Nov 18, 2008, at 5:10 AM, Roshan Sullad wrote:
> [...]
> I have another Visual studio test application where I am using this
> Sqlite3.dll functionality, I have linked statically to Sqlite3.dll by
> including *sqlite3.c,sqlite3.h,sqlite3ext.h* , files in to my test
> application project. And a
On Nov 25, 2008, at 1:44 PM, Igor Augusto Guzzo wrote:
> I get an ARM based embedded system (AT91SAM9260 - ATMEL), linux based,
> with uclibc library and my code, developed in C with the sqlite3
> library, runs fine only in my host linux (Fedora).
>
> Firstly, I compiled the code on Makefile proj
On Mar 12, 2009, at 12:01 AM, jonwood wrote:
> PaymentDate=2009/01/05
Note the '/'s
> And then I ran the following query:
>
> SELECT * FROM Payments WHERE FK_CustomerID=5 AND DATE(PaymentDate) >=
> DATE('2009-01-01') AND DATE(PaymentDate) <= DATE('2009-03-11')
Note the '-'s.
'2009/' > '2009-'
On Mar 12, 2009, at 12:08 AM, jonwood wrote:
> Doug Currie-2 wrote:
>>
>> Note the '/'s
>>
>
> What does this mean? What does DATE('2009-1-1') or DATE('2009/1/1')
> return?
> Does DATE() simply have no effect whatsoever?
Sorry to
On Apr 22, 2009, at 4:38 PM, Pavel Ivanov wrote:
> I've tried to set pragma synchronous = on (it's off by default for
> me), but it makes application to work 5 times slower which is not
> acceptable for me. I would be happy if there was some solution in
> between that, i.e. for example just a bit
On Dec 13, 2009, at 3:16 PM, Alexey Pechnikov wrote:
> As we can see, the unique index can check equlity of REAL values
> but the "=" operator can not. it's fantastic I think :-)
The problem is not the "=" operator...
sqlite> create table test (save_date REAL unique);
sqlite> insert into test
On Jan 4, 2010, at 6:35 AM, sasikuma...@tcs.com wrote:
> I'm using SQLite DB version 3.6.12. I recently read about the feature of
> In-Memory Database and tried to implement it. I was able to create a new
> DB connection in memory, able to create a table and insert some set of
> records into t
On Feb 15, 2010, at 1:43 PM, Roger Binns wrote:
> Shane Harrelson wrote:
>> I'm looking at how this can be improved.
>
> It seems that everyone else is converging on using David Gay's dtoa.c
We've been "converging" for a few years!
http://www.mail-archive.com/sqlite-users@sqlite.org/msg09529.h
On May 18, 2010, at 4:14 AM, Sylvain Pointeau wrote:
> but is it 64 bits? or do I have to add a special option?
Last time I built a Universal Binary sqlite3 on OS X (March 2010 3.6.22) I had
to
CFLAGS='-arch i686 -arch x86_64' LDFLAGS='-arch i686 -arch x86_64' ./configure
--disable-dependency
On Jun 1, 2010, at 2:24 PM, Gilles Ganault wrote:
> Actually, it's a Blackfin processor, and since it's an embedded
> environment, RAM and storage (NAND) are an issue.
You may find eLua interesting. http://www.eluaproject.net/
The supported platforms are heavily ARM based, but in the same perfo
On Aug 19, 2010, at 4:00 PM, David Bicking wrote:
> I haven't tried RAISE(ROLLBACK... as that seems to severe.
> RAISE(ABORT... removes the initial insert to Table1, which I want to avoid.
> RAISE(FAIL.. on lets say the fourth record inserted in to Table2, would leave
> the first three there, w
On Aug 24, 2010, at 10:57 AM, Nikolaus Rath wrote:
> Nikolaus Rath writes:
>> Still no one able to clarify the issues raised in this thread?
>>
>> Let me try to summarize what I still don't understand:
>>
>> - Will SQLite acquire and release an EXCLUSIVE lock while keeping a
>> SHARED lock i
On Nov 28, 2010, at 11:18 AM, Rick Regan wrote:
> Michael,
> Thanks for the very thorough analysis.
This is a difficult problem; fortunately it was solved 20 years ago...
http://www.mail-archive.com/sqlite-users@sqlite.org/msg09529.html
e
___
sqlite-
On Nov 28, 2010, at 5:37 PM, Rick Regan wrote:
> On Sun, Nov 28, 2010 at 4:01 PM, Doug Currie wrote:
>
>> On Nov 28, 2010, at 11:18 AM, Rick Regan wrote:
>>
>>> Michael,
>>> Thanks for the very thorough analysis.
>>
>> This is a difficult
On Nov 28, 2010, at 6:19 PM, Rick Regan wrote:
> On Sun, Nov 28, 2010 at 5:52 PM, Doug Currie wrote:
>
>>
>> There is a new publication on this subject that may be of interest to those
>> looking at providing solutions:
>>
>> http://portal.acm.org/citat
On Nov 29, 2010, at 9:37 AM, Rick Regan wrote:
> "For IEEE 754 double-precision numbers and 64-bit integers roughly
> 99.4% of all numbers can be processed efficiently. The remaining 0.6% are
> rejected and need to be printed by a slower complete algorithm."
>
> Hmmm. What's involved in the "sl
On Dec 7, 2010, at 10:49 AM, Csom Gyula wrote:
> It clarified the situation, that is backup-restore seems to be the best
> choice:) Just one more question. As you put backup-restore is based upon data
> pages (that could be binary a format I guess) not on plain SQL/data records.
> After all: I
On Mar 31, 2011, at 2:27 PM, Mike Rychener wrote:
> I have tried the latest Explorer and it gets a syntax error on STDEV.
> However, that function works in Eclipse just fine, to take the standard
> deviation of a column (like min, max, avg). Is there a workaround or
> other fix available?
On May 26, 2011, at 2:54 AM, Jan Hudec wrote:
> Gotcha! No, it's not. -1-x is equivalent, but -x-1 is not:
>
>sqlite> select -1-(1<<63), -(1<<63)-1;
>9223372036854775807|9.22337203685478e+18
>
> Besides my point was not that it's not possible, but that it would
> be more readable with de
> Before binding an address to a statement using sqlite3_bind_int64() I apply an
> offset to the address to translate it to a signed value. And when reading out
> an address using sqlite3_column_int64() I reverse the process. I.e.
> dbase_value = addr_value - offset
> addr_value = dbase_va
> The actual test I'm doing is something like:
> WHERE ?1 >= (base + begin) AND ?1 < (base + end)
> where ?1, base, begin, and end are all 64-bit addresses.
This is a test with a well known optimization for unsigned values:
WHERE (?1 - base - begin) < end
To make the < test unsigned i
Thursday, March 31, 2005, 5:53:12 PM, you wrote:
>> The actual test I'm doing is something like:
>> WHERE ?1 >= (base + begin) AND ?1 < (base + end)
>> where ?1, base, begin, and end are all 64-bit addresses.
> This is a test with a well known optimization for unsigned values:
> WHER
Tuesday, July 19, 2005, 12:19:48 PM, Aaron wrote:
> We are inserting records into SQLite databases, and in our testing
> have discovered that in some circumstances it is possible to be
> inserting records inside a transaction, yet not have the fact that
> the database journal file is growing b
Wednesday, August 10, 2005, 5:57:50 AM, Ivo wrote:
IK> Hello,
IK> It seems that at least under windows there are rounding problems with the
IK> milliseconds:
IK> sqlite> select strftime("%f", "2005-01-01 12:34:55.122");
IK> 55.121
IK> [...]
IK> Is this maybe a problem of the underlying c-libra
See http://lists.debian.org/debian-arm/2003/10/msg00030.html
ARM has at least two FL formats.
> from the ARM Architecture Reference Manual, Page C2-4:
>
> "The word order [for DP format] defined here for the VFP architecture
> differs from that of the earlier FPA floating-point architecture. In
Thursday, August 18, 2005, 3:18:56 PM, Frank wrote:
> I repeated the test using the value 1.2345678 in order to be
> able to identify the position of each byte:
> linux i386:
> 1bde8342cac0f33f
> 0100
> linux arm:
> cac0f33f1bde8342
> 0100
> So, it indeed looks like 32
KW> I downloaded the raw source and ran 'configure' and 'make' from a
KW> separate folder. The resulting output I copied to /usr/lib/sqlite. In
KW> it a see the bunch of .lo, .o and the two .la files (libsqlite3.la,
KW> libtclsqlite3.la)
KW> I am use to a Visual Studio build environment, but fro
elps). Common Lisp and Scheme
have rationals as well as real, complex, and arbitrary precision
integer numbers. http://mathworld.wolfram.com/RationalNumber.html
--
Doug Currie
Londonderry, NH
is to introduce a new static type, called
DYNAMIC, that permits any value. Summarizing and seconding Dennis
Cote's suggestion, perhaps columns that have no type declared, or that
are declared DYNAMIC, behave as SQLite does today, and columns that
have static declarations behave as if they are s
A brief report on building sqlite-3.3.4 with MinGW/MSYS and tcl84 on
WinXP...
1. After configure, a small edit was necessary to the Makefile; for
some reason libtool doesn't put .lo objects into .libs subdirectory
anymore; there was also an issue reported on the mailing list with
stripping the DLL
e);
> create index source_idx on Media (key,source);
> create index key_source_val_idx on Media (key,source,value);
I wonder what effect
create table Media (id INTEGER PRIMARY KEY, key, value, source integer);
would have on your query time. This would use the already built-in
BTree index.
e
--
t can't be improved.
> I couldn't agree more with you.
> Thanks for the help!
> Regards,
> -- Tito
--
Doug Currie
Londonderry, NH
Monday, October 27, 2003, 9:22:57 AM, D. Richard Hipp wrote:
> If you think about how a disk driver works, you'll quickly realize
> that to truly commit a transaction to the disk surface requires at
> least one revolution of the platter. So for a 5400 RPM disk drive,
> you will get (at most) 90 tr
> If you disable idx2, you will see that the inserts go much faster. I
> also observe that the journal file is about 1/3rd the size of the database,
> which is consistent with the observation that every disk block associated
> with idx2 needs to be changed. My TCL test script for this situation
>
Monday, November 3, 2003, 11:22:55 PM, Ben Carlyle wrote:
>> > Can any readers suggest ways that I have not thought of for making
>> > large numbers of non-localized INSERTs go faster?
>> Instead of journaling the old ("undo") pages of idx2, simply record
>> the fact that idx2 is modified (i.e.,
> Your suggestion was to reconstruct the index from original
> table data on a rollback. For a large transaction that touches
> most pages of the index, this can give (at best) a 2:1 speedup.
> But the other side, the potential slowdown is extreme.
Yeah, there is that drawback. Other DBMSs avoid
My uses of SQLite are multithreaded (mostly) single process. So, an
approach that would appeal to me is "client-server" where the server
is a thread in my process, and the clients are other threads. Adding
a lock manager to the server thread would permit fine grained locking
with ACID properties.
> Please, give me some examples of the kinds of things you are
> doing which could benefit from improved concurrency.
One typical application for me is data recording for regulatory
compliance (FDA 21 CFR 11). Instruments are polled or issue data
frequently, say once a second. Data from several of
It looks to me that several users are (a) in a uniprocess environment,
and (b) inventing their own SQLite db access synchronization code. An
SQLite fine grained lock manager for threads in a single process would
address these same issues, with better concurrency as well.
Jay said:
> All database a
Thursday, November 27, 2003, 5:21:46 AM, Dennis Volodomanov wrote:
> [...]
> 8<
> unsigned char out[15000];
> memcpy((BYTE*)&out,mybuf,photo_length);
> out[photo_length]='\0';
> int size=sqlite_decode_binary(out,out);
> if(size<0)
> {
> // now we don't even get here
> }
> 8<
If
Thursday, November 27, 2003, 10:19:22 PM, Dennis Volodomanov wrote:
>> and sqlite_decode_binary() wants an unsigned char. Can you help me
>> and tell me what to do in order to supply sqlite_decode_binary()
>> with the data it wants in a correct fashion?
> Well, I did just cast it to an unsigned
> [...]
> I'm really lost on how to handle this parent->child relationship
> using standard SQL.
See
> Trees in SQL
> Joe Celko
> 23 Feb 2001
> Rating: -4.52- (out of 5) Hall of fame tip of the month winner
http://searchdatabase.techtarget.com/tip/1,289483,sid13_gci537290,00.html
Also see a thr
Ticket #433 http://www.sqlite.org/cvstrac/tktview?tn=433 attachments
have been updated with diff files for sqlite 2.8.8. These files are
updated configure.ac configure and Makefile.in for mingw/msys on
Windows (although the updated files are intended to work on any
platform supported by the present
I had to change test4.c line 18, adding "OS_UNIX==1"...
#if defined(OS_UNIX) && OS_UNIX==1 && defined(THREADSAFE) && THREADSAFE==1
After that change, it built and the test ran (although it didn't run
any thread test cases, just skipped them). This is on Windows with
mingw/msys.
e
Friday, Decem
Eugene,
> create table test(a int, b datetime);
> insert into test values(1,'2004/1/3');
> select * from test where date(b)='2004/1/3'
> The SELECT statement returns no record.
But this works:
sqlite> select * from test where b='2004/1/3';
1|2004/1/3
The date is not encoded properly in the dat
Here are some clarifications about date and time functions.
SQLite stores everything in the database as a string. You may choose
to represent your datetimes in the database as Julian dates or as
datetime formatted strings. Julian dates are doubles, but they are
converted to and from string when wr
> any plans/desires to fix this
I hesitate to announce this for reasons I'll explain below, but I have
been working on an experimental version on the SQLite pager called the
Shadow Pager. The Shadow Pager is intended to address this problem for
applications that use SQLite from a single process on
See: http://sqlzoo.net/
A Gentle Introduction to SQL
e
Wednesday, January 14, 2004, 2:22:23 PM, you wrote:
> Been all through the wiki and didn't find any
> first-time-get-you-started-basic-how-to. Thanks though.
-
To unsubscr
Monday, March 22, 2004, 1:46:00 PM, Mark wrote:
>> I have run experiments to see how much faster SQLite might
>> work if it didn't invalidate its cache so quickly. The
>> answer is about 15%. So it is probably worth looking into
>> someday. Note that such a change will be backwards but
>> not f
Thursday, March 25, 2004, 1:33:03 AM, Rohit wrote:
> I was going thru the pager source code ( pager.c ). The comments include
> references to "Journal", "Transaction Journal", "Checkpoint Journal". What
> is the difference between the three? Am I missing something?
There is only one journal file
Here is what I did to try to recreate your problem after building the
sqlite dll with the usual ../sqlite/configure make procedure.
I downloaded the C/C++ magazine March example file, and extracted
Owen.txt. I cut example 'Listing 2: C API example' and commented out
the redundnant defintion of sql
> way, the mapping table would be the responsibility
> of the pager layer which (up until now) has known
> nothing about the btree layer. But with this approach,
> the pager layer would need to call the btree layer
> recursively. Thinking about that is starting to
> make my head spin.
> Does any
sqlite> select datetime(1080701286,'unixepoch');
2004-03-31 02:48:06
sqlite> select datetime(1080701286,'localtime');
2954147-07-10 07:00:00
sqlite> select datetime(1080701286,'unixepoch','localtime');
2004-03-30 21:48:06
sqlite> select julianday('now');
2453095.66955468
sqlite> select datetime(245
Monday, April 5, 2004, 6:13:18 AM, Christian Smith wrote:
> On Wed, 31 Mar 2004, Joel Lucsy wrote:
>>Just for the record, for Windows machines, only NTFS v5 formatted
>>drives/partitions support sparse files. Windows 2000 or better are the
>>only ones supporting NTFS v5. This means Win9x and FAT3
mission to distribute it. Perhaps his web page will come back on
line soon. http://www.cs.hut.fi/~ylo
e
> Cheers,
> Christian
> On Mon, 5 Apr 2004, Doug Currie wrote:
>>Monday, April 5, 2004, 6:13:18 AM, Christian Smith wrote:
>>
>>> On Wed, 31 Mar 2004, Joel L
Friday, April 9, 2004, 6:54:44 AM, D. Richard Hipp wrote:
> Nuno Lucas wrote:
> > I have a feature that would be nice in a 2.8.x version, but I can live with
> > it if only on 3.0. It's the optimization for the many times used "SELECT
> > COUNT(*) FROM ...", at least if FROM is a table or a vi
> D. Richard Hipp wrote:
>>
>> My thoughts on BlueSky have been added to the wiki page:
>>http://www.sqlite.org/cvstrac/wiki?p=BlueSky
I added some responses; I do not agree with Richard's concerns about
Shadow Paging, and I corrected some mistaken conclusions. I apologize
if my paper was not
Wednesday, April 14, 2004, 1:16:54 AM, Andrew Piskorski wrote:
>[...]
> Doug Currie's "Shadow Paging" design sounds promising.
> Unfortunately, I have not been able to download the referenced
> papers at all (where can I get them?),
There are three sources for the papers. The two links on the wi
Thursday, April 15, 2004, 1:47:01 PM, rich coco wrote:
> this is a bit off topic i suppose, but here goes...
> does anyone know of an open-source translation toolkit
> that ultimately would generate code to map XML to/from SQL?
> Or maybe i am not phrasing the question properly.
> What I am loo
Thursday, April 15, 2004, 9:16:01 AM, Christian Smith wrote:
> On Wed, 14 Apr 2004, Doug Currie wrote:
>>One way to get table level locking without a great deal of pain is to
>>integrate the shadow paging ideas with BTree management. Rather than
>>using page tables for the
Firebird 1.5
SQL> CREATE TABLE test1(a VARCHAR(100));
SQL> INSERT INTO test1 VALUES('501');
SQL> INSERT INTO test1 VALUES(' 502 ');
SQL> SELECT * FROM test1 WHERE a=501;
A
===
501
SQL> SELECT * FROM test1 WHERE a=502;
Results from Firebird 1.5 (thanks for the syntax, Andrew)...
SQL> select '500' = 500;
Statement failed, SQLCODE = -104
Dynamic SQL Error
-SQL error code = -104
-Token unknown - line 1, char 14
-=
SQL> select 500 = '500';
Statement failed, SQLCODE = -104
Dynamic SQL Error
-SQL error code = -104
-
> Does anyone know how to open a connection to sqlite database from Python in write
> mode?
Did you remember to commit your writes?
import sqlite
cx = sqlite.connect('test.db')
cu = cx.cursor()
cu.execute('create table t1 (a,b,c)')
cu.execute('insert into t1 values (1,2,3)')
cx.commit()
cu.
> Hi, is there an archive of this list somewhere?
http://www.mail-archive.com/[EMAIL PROTECTED]/
e
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> If I make use of alloca() in SQLite version 3, will this
> cause any extreme hardships? Who is using a C compiler to
> build SQLite that does not support alloca()?
Warning: there are gcc bugs in the x86 optimizer related to alloca(). E.g.,
https://sourceforge.net/tracker/?func=detail&atid=10243
Saturday, June 19, 2004, 11:35:22 AM, Nuno wrote:
> func-13.4...make: *** [test] Segmentation fault
> [EMAIL PROTECTED] $ uname -a
> Linux tux 2.4.25_pre7-gss-r5 #5 SMP Tue Jun 8 22:48:33 GMT 2004
> i686 Pentium II (Klamath) GenuineIntel GNU/Linux
> -
There are several build options in the configure/make of sqlite3 that
are obsolete, and others that are missing.
ENCODING is obsolete since it is specified in the open calls now.
There are still several references to it, though, in the make and
autoconf files, and these should all be removed.
INM
1 - 100 of 178 matches
Mail list logo
