Hi,
I think I may have found a bug where affinities change through the HAVING
expression. For example, under v3.6.22, if I do...
create table t1(a text, b int);
insert into t1 values(123, 456);
select typeof(a), a from t1 group by a having ab;
then I get integer|123 when I would expect
Alexey,
I can certainly tell you what is causing this behaviour:
When sqlite does a comparison, it checks the *column* affinity from both
sides. In your example, neither sides come from a column, but are
constants. Therefore, sqlite uses the NONE affinity on comparison (I
think, but I
Now, it is probable that the core can be patched as you request by
assigning affinity to constants during parsing, but I haven't had an
opportunity to look into it and I would have to check very
thoroughly that it will not brake something else if I do patch it
for you. At this precise
Hi,
I spotted this while looking into something else for Alexey:
The following sql is supposedly valid:
select 1 in (1)'hello';
where as
select * from t where 1 in (1)'hello';
returns Error: near 'hello': syntax error (which I would expect!)
This occurs on v3.6.22, but I haven't checked it
The following sql is supposedly valid:
select 1 in (1)'hello';
Apparently this gets interpreted as
select (1 in (1)) as hello;
(as is optional), under SQLite's long-standing policy of
accepting single and double quotes more or less
interchangeably.
Hmm, I'd not have guessed. Thanks -
Hi,
I understand from reading http://www.sqlite.org/c3ref/value.html that
there is a distinction between protected and unprotected value objects,
and that some api interfaces, notably sqlite3_value*, require the former
and others, notably sqlite3_column*, provide the latter.
What I would
Igor Tandetnik wrote on 24/02/2010:
Well, too bad.
Ha! Nothing's that bad!!!
Protected means a mutex is held while the value is outstanding.
If such a hypothetical API existed, it would mean you could instruct
SQLite to hold a mutex for an indefinite period of time, thus
blocking all
Igor Tandetnik wrote on 24/02/2010:
I must admit I have no idea what you are talking about, you lost me
thoroughly. In any case, mutex or no mutex, the pointer returned by
sqlite3_column_value is only valid until you step away from that row
or reset the statement. You can't hold onto the
Hi,
I've noticed in alter.c, around about line 480 there is a direct reference
to updating the sqlite_master table, rather than using the SCHEMA_TABLE
macro.
I wondered whether this was a simple oversight, or by design?
It means the following currently happens...
sqlite pragma
Hi,
I've spotted a very few places where the use of realloc or sqlite3_realloc
*may* constitute memory leaks if the realloc fails. Hope this helps;
please ignore if I've misread the code...
Line numbers should correlate to version 3.6.22, but I've included the
name of the function the line
Hi, not a major one, but...
version 3.6.22 has not been tagged as release in the fossil repository
(e.g. in http://www.sqlite.org/src/timeline?t=release).
Cheers
Will
___
sqlite-users mailing list
sqlite-users@sqlite.org
Hi people,
I think I may have found a bug in v3.6.21 of Sqlite, but would someone be
able to kindly verify my findings for me.
If I do the following...
CREATE TABLE t1 (c1 TEXT UNIQUE);
CREATE TABLE t2 (c2 TEXT UNIQUE);
INSERT INTO t1(c1) SELECT a
UNION ALL SELECT b;
INSERT INTO t2(c2)
- Message from Alexey Pechnikov pechni...@mobigroup.ru on Tue,
15 Dec 2009 22:14:07 +0300 -
To:
General Discussion of SQLite Database sqlite-users@sqlite.org
Subject:
Re: [sqlite] Gauging interest in patches...
Hello!
On Tuesday 15 December 2009 19:17:31
Hello again,
I have also checked this with 3.6.17 (which works) and 3.6.18 (which
doesn't), so it may be something that slipped in between these two
versions.
In case it is helpful, I'm running of the release checkouts from the
fossil repository. The configure is called with
Hi all,
This is a quick email just to gauge interest in a number of patches I've
created for Sqlite over the last year or so. What I want to know is
whether anyone would like me to post one or more of these patches here? I
have thought about posting to http://www.sqlite.org/contrib but since
John Brooks wrote on 15/12/2009 15:13:05:
I love the idea of READONLY and ENFORCE. I would certainly make use of
those in amalgamation form. What license do you put these under?
You should really publish these all somewhere, there are some great
features. Good work.
Thank you.
I have made
John Brooks wrote on 15/12/2009 15:13:05:
What license do you put these under?
Sorry, I forgot to say in my last email: I'm happy for these to end up in
the public domain like Sqlite -- I don't think realistically I could do
otherwise given the blessing-style licence that the main Sqlite
Alexey Pechnikov wrote on 15/12/2009 15:15:42:
3. ENFORCE constraint for table columns, for example: CREATE TABLE t(i
enforce integer, j enforce text). This optional constraint enforces
type
checking so that an entry must match the column type (i.e. integer,
real,
numeric, text, blob).
D. Richard Hipp wrote on 15/12/2009 17:05:31:
(1) Have your patches been fully documented and have you generated
automated test cases that provide 100% MC/DC and branch test
coverage? I'm guessing not and yet those are requirements for new
features in the core.
I believe they are fully
Hello,
Playing around with attached databases in sqlite 3.6.17, I notice that it
is possible to create triggers that operate across attached databases, but
not views. So something along the lines of:
attach database other.db as other;
create table other.a(a integer);
create table b(a
Alexey Pechnikov wrote on 30/11/2009 19:58:15:
This feature was disabled becouse can produce inconsistent database
schema.
If you want to enable this feature then the patch is simple:
--- sqlite3-3.6.20.orig/src/attach.c
+++ sqlite3-3.6.20/src/attach.c
@@ -447,10 +447,11 @@
if(
Yes, see the zErrMsg member:
http://sqlite.org/c3ref/vtab.html
Thank you! So simple, and I missed it ;o)
Will
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Hi,
Is it possible / can it be possible to set the error message (as would
then be read by a call sqlite3_errmsg) from within a virtual table
implementation. For example, inside the xUpdate function when some
constraint violation has occurred, to give a more accurate error message
than the
Hello,
I have a question regarding a modification I've made to the ATTACH
DATABASE command in Sqlite. The attached diff file (set against version
3.6.17) shows the modifications I've made, which I hope can be read quite
simply.
The modification involves adding an optional READONLY keyword;
24 matches
Mail list logo
