On Mar 28, 2005, at 6:15 AM, Jay wrote:
I didn't add it to Sqlite, I added it to the class that makes
up the application that uses sqlite. If you want the c or c++
code it's freely available on the internet.
One could probably compile PCRE into SQLite...
http://www.pcre.org/
Regards,
David
On Mar 17, 2005, at 2:08 PM, Clay Dowling wrote:
strftime(buffer, size, "%Y-%m-%sT%H:%M:%S", now);
SOAP uses the same format for date/time information, and I've been neck
deep in SOAP for the last few weeks.
I note that the newly released SQLite 3.2.0 addresses this issue. The
"T" is now allowed.
On Mar 18, 2005, at 1:49 PM, [EMAIL PROTECTED] wrote:
I don't believe that the sqlite bug-reporting system is currently set
up to
provide bug tracking on an individual person basis.
Ah, okay then. Feature request! :-)
On Mar 18, 2005, at 2:24 PM, Lawrence Chitty wrote:
Cvstrac, the bug tracking sy
On Mar 18, 2005, at 1:31 PM, Witold Czarnecki wrote:
You don't need to register. Just place the ticket:
http://www.sqlite.org/cvstrac/tktnew
I did that before, but then I received no notifications when the ticket
was updated or resolved. I'd love to get that information in the
future...
Thanks,
Hi All,
I'd like to file a bug report for SQLite, but do it as myself, so that
I (hopefully) will receive emails whenever the ticket is updated. (I
recently encountered a bug when I upgraded to 3.1.x, and then
discovered that it wasn't a bug, but a bug fix--for a bug report I had
filed!) Howeve
On Mar 17, 2005, at 4:27 PM, Kurt Welgehausen wrote:
Well, I might as well use the substr() function, then ...
Yes, unless you think %m is more expressive than 6,2 or
you want to extract more than one component.
sqlite> select * from datetest;
k d
-- ---
1
On Mar 17, 2005, at 2:59 PM, Kurt Welgehausen wrote:
Sorry, I misunderstood the context.
No problem.
sqlite> select * from datetest;
k d
-- ---
1 2005-03-17T16:21:30
sqlite> select strftime("%m", substr(d,1,10)||' '||substr(d,-8,8))
...>
On Mar 17, 2005, at 2:21 PM, Matt Sergeant wrote:
You can force the binding type in DBD::SQLite - see the DBI docs (grep
for ":sql_types").
True, but in our application, that would require a lot more
book-keeping than we'd like. Adding "+0" seems to do the cast we need
to keep up with how DBD::S
On Mar 17, 2005, at 2:24 PM, Kurt Welgehausen wrote:
Yes, I know it supports it without the "T" ...
sqlite> select strftime("%Y-%m-%dT%H:%M:%S", 'now', 'localtime');
strftime("%Y-%m-%dT%H:%M:%S", 'now', 'localtime')
-
2005-03-17T16:21:30
No:
sqlite> s
On Mar 17, 2005, at 1:23 PM, Kurt Welgehausen wrote:
strftime doesn't support the ISO-8601 format ...
I does if you give it the correct format string.
Yes, I know it supports it without the "T", but ISO-8601 mandates the
presence of the T.
Regards,
David
On Mar 17, 2005, at 11:40 AM, Clark Christensen wrote:
Probably off-topic for a SQLite list :-)
I'm not sure Perl will cast a non-numeric string
("2005-03-22T00:00:00") to a number. What number are you
looking for?
Actually the code that was cast was "substr(a, 6, 2)", which was
evaluating to "03
Hi All,
Given the below script (using DBD::SQLite 1.08, which uses SQLite
3.1.3), the output is just:
+0 Cast: 2005-03-22T00:00:00
I'm wondering, however, if unary + shouldn't also be able to cast an
expression to a number...shouldn't it?
Thanks,
David
#!/usr/bin/perl -w
use strict;
use DBI;
On Jan 28, 2005, at 6:03 PM, David Wheeler wrote:
On the other hand, I don't see why
collation info for a simple column reference can't be
made availabe through a view, since type info already
is available -- but I certainly could be missing
something.
It makes sense to me.
Bug report f
On Jan 28, 2005, at 12:04 PM, Kurt Welgehausen wrote:
Yes, it seems to me that views should respect the configurations of
their underlying tables, including collations, triggers, and the like.
I'll submit a bug report.
It's not quite that simple. A view column may be an
expression, and inferring at
On Jan 28, 2005, at 10:53 AM, Kurt Welgehausen wrote:
David,
No, you can't specify a collation when creating a
view (http://www.sqlite.org/lang_createview.html).
I don't know whether is was intentional that simple
columns in a view don't get collation info from the
base table, but if you think it's
On Jan 26, 2005, at 8:56 AM, David Wheeler wrote:
sqlite> create table a(b text COLLATE nocase);
sqlite> insert into a values ('this');
sqlite> insert into a values ('This');
sqlite> insert into a values ('THIS');
sqlite> select * from a where b = &#
On Jan 23, 2005, at 7:29 PM, David Wheeler wrote:
sqlite> create table a(b text COLLATE nocase);
sqlite> insert into a values ('this');
sqlite> insert into a values ('This');
sqlite> insert into a values ('THIS');
sqlite> select * from a where b = &#
On Jan 23, 2005, at 1:02 PM, D. Richard Hipp wrote:
Use sqlite3_create_collation() to register a collating sequence
that ignores case in UTF-8 characters. Then put "COLLATE "
after the declaration of the column you want to be caseless.
Thanks. This works for me in English, at least:
sqlite> create
Hi All,
Apologies for the newbie questions...
What's the best way to do case-insensitive searches in SQLite, given
that LOWER() may not work properly with UTF-8 characters? Is LOWER()
the best way in general, anyhow? And if so, will it use indexes?
Many TIA,
David
On Jan 22, 2005, at 11:13 PM, Jeff wrote:
Here is the question: Should I store XML files in a database, or
should I just put it on the file system. Which would be faster?
The file system would be faster, since SQLite sits on top of it,
anyway, so you have its overhead no matter what.
Regards,
Dav
SQLiters,
First of all: Rocking great RDBMS. I love it!
Now, to my question. I'm confused about the typelessness of SQLite,
because I've found a place where the type *does* seem to matter. This
example demonstrates the issue:
sqlite> create table foo (age int);
sqlite> insert into foo values (7)
21 matches
Mail list logo
