On 09.05.2014 12:36, Carlos Ferreira wrote:
I am using a win32 DLL built sqlite-dll-win32-x86-3071700 . the DLL is
from 20-5-2013.
I am using it with Delphi, and it works fine for what I need.
I need however a 64 bits version of the DLL.
SQLite3 for Delphi, both Win32 and Win64, with many
On 09.05.2014 13:50, Carlos Ferreira wrote:
XE6 itself seems to native have access to both...
FireDAC only, and outdated by 2 months at the day of release. Delphi XE5
SQLite is still at 3.7.17, almost one year behind.
DISQLite3 has always been up to date for years and Delphi versions back
On 24.01.2014 10:06, Max Vlasov wrote:
BCC 5.5 (freely downloadable) compiles any version of sqlite3 to
object files linkable to Delphi 5 and later, the only drawback I
noticed is that for memory-intensive operations (memory databases) the
performance is twice as worst comparing to the dll on
On 23.01.2014 11:28, dean gwilliam wrote:
More specifically...is there the equivalent of that powerbasic include
file for D5 i.e. that enables you to access the dll's function calls
unchanged?
Failing that...anything that will let me work with the latest sqlite 3 dll
The meaner and leaner...the
SQLite 3.8.1 compiled with SQLITE_OMIT_FLAG_PRAGMAS #defined calls
sqlite3_busy_timeout() for all flag pragmas.
Example:
PRAGMA legacy_file_format=100;
should do nothing but sets
sqlite3_busy_timeout(db, 100);
The change was introduced here:
On 10.10.2013 03:53, Richard Hipp wrote:
I think that http://www.sqlite.org/src/info/e97d7d3044 fixes this issue.
Works well for me.
Please correct me if I've missed something.
You committed to the row-size-est branch. I guess this will be merged
into trunk for 3.8.1?
Ralf
analyze.c always prints 32-bit variables as 64-bit here:
http://www.sqlite.org/src/artifact/d322972af09e3f8debb45f420dfe3ded142b108b?ln=746
http://www.sqlite.org/src/artifact/d322972af09e3f8debb45f420dfe3ded142b108b?ln=792
This can cause wrong sqlite_statX tables which I have experienced
On 09.10.2013 15:50, Eric Minbiole wrote:
With this change, tests pass again:
#if sizeof(p-nRow) == sizeof(long long)
sqlite3_snprintf(24, zRet, %lld, p-nRow);
#elseif sizeof(p-Row) = sizeof(long)
sqlite3_snprintf(24, zRet, %ld, p-nRow);
#else
sqlite3_snprintf(24,
I suggest a verb to express what the function is actually doing, namely
to reduce its argument in rank or degree for the query planner:
DEGRADE
1. to reduce in worth, character, etc; disgrace;
2. to reduce in rank, status, or degree; remove from office;
3. to reduce in strength, quality,
On 11.09.2013 16:07, Ryan Johnson wrote:
Perhaps you meant demote rather than degrade ? That would be a
better fit (an external action that does not necessarily make the
object worse or less useful), and less vague, but it still carries a
negative connotation.
demote sounds fine to me,
On 19.07.2013 09:21, Sqlite Dog wrote:
Our database manager is developed using Delphi (Pascal). Thus it is
not possible to statically link SQLite library, SQLite.dll is used.
Is there some other way to support SEE in our project?
You have two options:
* Create your own sqlite.dll and
On 19.07.2013 15:27, Sqlite Dog wrote:
* Statically link SQLite to your Delphi application. My DISQLite3
enables you to do just that and has numerous extensions: One is a
custom encryption algorithm. This is not compatible with SEE,
but if you like I can replace it with your original
On 19.06.2013 17:18, Tom Holden wrote:
I use the SQLiteSpy compilation of SQLite3 which recently upgraded
from pre SQLite 3.7.8 to pre 4.2.0.
You must be mistaken. As the author of SQLiteSpy, I can clearly say that
there is no SQLiteSpy version 3.7.8 nor 4.2.0. The current version is
On 21.06.2013 05:10, Tom Holden wrote:
Ralf Junker ralfjunker at gmx.de Thu Jun 20 18:44:15 EDT 2013 wrote:
On 19.06.2013 17:18, Tom Holden wrote:
I use the SQLiteSpy compilation of SQLite3 which recently upgraded
from pre SQLite 3.7.8 to pre 4.2.0.
You must be mistaken. As the author
The new fts3tokenize virtual table calls the fts3_tokenizer() SQL function
internally to retrieve the pointer to the tokenizer implementation for a FTS
table:
http://www.sqlite.org/src/artifact/a29f126b9e6c6a6f1021a8f7440bf125e68af1f9?ln=74-100
However, this call is rejected if, for security
Current trunk still does not compile with SQLITE_OMIT_WAL #defined.
Details here:
http://www.mail-archive.com/sqlite-users@sqlite.org/msg76672.html
Ralf
On 26.04.2013 17:34, Richard Hipp wrote:
Please visit http://www.sqlite.org/draft/releaselog/3_7_17.html to see the
proposed enhancements
I am unsure about how the amatch extension works. According to the
documentation, I believe that the SQL below should return at least one
record, but it does not. No errors are reported either.
I compiled the shell executable with the 201304290917 draft amalgamation
and today's amatch.c from
The current SQLite Fossil snapshot does not compile with SQLITE_OMIT_WAL
defined.
Reason:
The Pager-pWal element is compiled out in pager.c here:
http://www.sqlite.org/src/artifact/6c3a8a5d665498b0344395a2c9f82d5abc4cc771?ln=691-694
but still accessed here:
In the list of PRAGMAs in
pragma.html
the PRAGMA user_version documentation link to
http://www.sqlite.org/pragma.html#pragma_user_version
is invalid. It should point to
http://www.sqlite.org/pragma.html#pragma_schema_version
instead.
This is also present in today's documentation
I know that AsyncIO is now superseded by WAL [1], but according to
Richard it should still work for existing applications [2].
However, I experience the opposite.
The small C application below runs well when linked against SQLite
3.7.14. With SQLite 3.7.15, it mysteriously fails. I see two types
I experience problems with Async IO testing the latest 3.7.15 trunk.
Simple statements like CREATE TABLE fail with SQLITE_IOERR.
I read the note in the Async IO README.txt that Async IO is now
superceded by WAL mode and no longer maintained.
Does this also mean that it will no longer be working
On 04.12.2012 22:14, Richard Hipp wrote:
Does this also mean that it will no longer be working with SQLite
3.7.15? Is it just deprecated for new development? Or has something else
changed that I should take care of?
That means that we are not willing to devote large amounts of time to it
On 04.12.2012 22:25, Richard Hipp wrote:
My question is if existing applications which Async IO should continue
to work with SQLite 3.7.15? Or has something in the SQLite core changed
so that you'd expect Async IO failures in 3.7.15, or later versions?
They should continue to work, as far
On 02.12.2012 04:37, Simon Slavin wrote:
I'm using DISQLite and the online api in delphi, not the command
line thing.
I have seen some bad drivers which assume that underlying schema will
not be changed by another user while they have a database connection
open. I have no reason to believe
On 26.06.2012 14:33, Vivien Malerba wrote:
The code is some SQL entered by the user, I have no control over it. There
is effectively the possibility to parse the SQL entered, detect the CREATE
table statement and act accordingly, but I would like to see if SQLite has
some kind of builtin
Testing SQLite Fossil [0abdc2903d], sqlite_open_v2() returns SQLITE_PERM when
trying to open a named memory database if the flag SQLITE_OPEN_CREATE is not
passed. This is in contrast to unnamed memory databases. Is this intentional?
Basic C code below demonstrates the issue.
Ralf
... at both end and beginning of these lines:
http://www.sqlite.org/src/artifact/45a846045ddb8c4318f2919f3a70f011df5ca783?ln=2584-2585
Ralf
___
sqlite-users mailing list
sqlite-users@sqlite.org
On 04.05.2012 16:39, Richard Hipp wrote:
If a single min() or max() aggregate function appears in a query, then any
other columns that are not contained within aggregate functions and that
are not elements of the GROUP BY will take values from one of the same rows
that satisfied the one min()
On 27.04.2012 11:38, Gabriel Corneanu wrote:
There is one more reason to use DLLs, I'm surprised noone mentioned it.
What if you don't use C??? (I use myself Delphi with a header conversion).
DISQLite3 compiles right into your Delphi application. Both 32-bit and
64-bit supported:
On 27.04.2012 15:08, Gabriel Corneanu wrote:
With the amalgamation, it's also quite easy to compile to one obj and
link directly in Delphi (similar to jpeg; that's probably what you also
do). No pun intended, why should I pay for it?
- DISQLite3 Personal edition if free!
- DISQLite3 is
On 05.03.2012 14:50, Rob Richardson wrote:
I keep hoping to find something better, because SQLiteSpy does not
offer the ability to edit a table inside a grid.
Not quite true. SQLiteSpy can edit table cells inside a grid.
Double-click the table-icon in the schema treeview to display the table.
On 05.03.2012 16:11, Rob Richardson wrote:
With the latest version, I think you can.
SQLiteSpy grid editing has been around for years, it is available since
version 1.6.0., 7 Feb 2007.
But I haven't been able to get the latest version. The link you
provided does not work for me. Do you know
On 05.03.2012 18:45, Rob Richardson wrote:
I can't get to www.yunqa.de now. I tried in IE8 and FireFox.
Most strange. Luckily, search engines find plenty of SQLiteSpy download
alternatives. Here is one of the more well known ones:
On 13.02.2012 10:18, Dan Kennedy wrote:
On 02/10/2012 11:06 PM, Ralf Junker wrote:
The new feature to insert multiple rows of VALUES in a single INSERT
http://www.sqlite.org/src/info/eb3b6a0ceb
gives wrong results if SQLite is compiled with
SQLITE_OMIT_COMPOUND_SELECT.
Has the team
On 07.02.2012 12:28, Ralf Junker wrote:
The new feature to insert multiple rows of VALUES in a single INSERT
http://www.sqlite.org/src/info/eb3b6a0ceb
gives wrong results if SQLite is compiled with SQLITE_OMIT_COMPOUND_SELECT.
Has the team seen this or has it been overlooked? Shall I
The new feature to insert multiple rows of VALUES in a single INSERT
http://www.sqlite.org/src/info/eb3b6a0ceb
gives wrong results if SQLite is compiled with SQLITE_OMIT_COMPOUND_SELECT.
Example:
CREATE TABLE t10(a,b,c);
INSERT INTO t10 VALUES(1,2,3), (4,5,6), (7,8,9);
SELECT * FROM
The sqlite3_uri_int64() doc reads: If the value of P is something other
than an integer, then zero is returned. I found this to be not true.
Instead, it returned default.
Ralf
___
sqlite-users mailing list
sqlite-users@sqlite.org
Reading the sources, sqlite3_db_release_memory() always returns
SQLITE_OK. Will it stay this way or will it some day return another
value like the amount of memory released?
Ralf
___
sqlite-users mailing list
sqlite-users@sqlite.org
VACUUM with multiplex does not delete chunks on Windows (fossil [8ce2b74a82]).
It seems this is because the file handle(s) are still held open by the
multiplex layer when xDelete is triggered. Since Windows can not delete open
files, they are kept.
I have not investigated this in depth, but
For me, this test from test/exists.test fails if both database
connections are opened in WAL mode, that is if PRAGMA journal_mode=WAL
is issued right after each DB is opened.
# TABLE objects.
#
do_test{
sql1 { DROP TABLE IF EXISTS t1 }
sql2 { CREATE TABLE t1(x) }
sql1 {
The test passes well if I recreate the database file anew just prior to
running it so it acts upon an empty database.
If this is what is intended, I apologize for the false alarm.
Ralf
On 10.04.2011 10:28, Ralf Junker wrote:
For me, this test from test/exists.test fails if both database
For me, this test from test/exists.test fails if both database
connections are opened in WAL mode, that is if PRAGMA journal_mode=WAL
is issued right after each DB is opened.
# TABLE objects.
#
do_test{
sql1 { DROP TABLE IF EXISTS t1 }
sql2 { CREATE TABLE t1(x) }
sql1 {
(*.dll).
Visit the DISQLite3 Internet site for latest information and updates:
http://www.yunqa.de/delphi/
Copyright (c) 2011 Ralf Junker, Delphi Inspiration del...@yunqa.de
- }
program DISQLite3_Very_Large_Integer
There are far too many checked out. in the following docs, probably
left-overs from copy-paste operations:
** ^(dtSQLITE_DBSTATUS_LOOKASIDE_HIT/dt
** ddThis parameter returns the number malloc attempts that were
** satisfied using lookaside memory. Only the high-water value is meaningful;
**
This SQL:
drop table if exists t11;
CREATE VIRTUAL TABLE t11 USING fts4;
INSERT INTO t11 VALUES('quitealongstringoftext');
INSERT INTO t11 VALUES('anotherquitealongstringoftext');
UPDATE t11_stat SET value = X'';
SELECT matchinfo(t11, 'nxa') FROM t11 WHERE t11 MATCH 'a*';
leads
Recent changes to FTS3 apparently require that SQLite must be compiled
with pager pragmas, otherwise FTS3 will cause a division by zero
exception as I have experienced right now.
This means that the FTS3 extension can crash an application if the core
SQLite library is compiled with
Check-in [876845661a] (http://www.sqlite.org/src/info/876845661a) is
incomplete: fts2_tokenizer.c still contains calls to isalnum() and
tolower() for FTS2.
FTS1 also #includes ctype.h, just in case you care to remove it from
SQLite completely. The changes are just like for FTS2.
Ralf
On 11.09.2010 20:42, Stef Mientki wrote:
is there a program that converts sqlite database from windows-1252 to utf-8?
Yes, SQLiteSpy does this:
* Open database file
* Menu Execute - Text to Unicode Conversion.
* Select tables and columns to convert.
* Choose database codepage.
* Press OK to
SQLite 3.7.2 has a regression with journal_mode=off and
locking_mode=exclusive. Here is the SQL reproduce:
drop table if exists t1;
PRAGMA locking_mode=exclusive;
pragma locking_mode;
CREATE TABLE t1(a PRIMARY KEY, b);
PRAGMA journal_mode = off;
BEGIN;
INSERT INTO t1 VALUES(13,
On 27.08.2010 18:58, Noah Hart wrote:
http://www.sqlite.org/pragma.html#pragma_journal_mode states
The OFF journaling mode disables the atomic commit and rollback capabilities
of SQLite. The ROLLBACK command no longer works; it behaves in an undefined
way. Applications must avoid using the
Related to constraint violations, an error message returned by
sqlite3_errmsg() changes to the better after calling sqlite3_reset() or
sqlite3_finalize().
Example code is below, here is the output:
sqlite3_step: 19 constraint failed
sqlite3_reset:19 t.c may not be NULL
This is SQLite 3.6.23.1 compiled with SQLITE_ENABLE_UPDATE_DELETE_LIMIT
(plus a few others, which should not matter to the problem).
The UPDATE ... LIMIT clause works fine when applied to tables, but
suppresses any updates when applied to a view with an update trigger.
Here is some example
We just experienced the hard way that overloading certain built-in SQL
function can interfere with core SQL commands if the overloaded function
behaves differently from the built-in function.
Not surprising, after looking at the sources:
* ALTER TABLE - alter.c uses SUBSTR and LIKE.
* VACUUM
Thanks to both Scott and Dan for your answers!
Ralf
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
The recent changes to FTS3 fixed a long standing problem with MATCH and
AND operators combined. Take this schema:
drop table if exists myfts;
create virtual table myfts using fts3 (a);
insert into myfts values ('one');
insert into myfts values ('two');
This following query produced an unable to
The current Fossil trunk [dd4962aa34] does not compile with both
* SQLITE_OMIT_PAGER_PRAGMAS
* SQLITE_OMIT_VACUUM
enabled. These defines exclude btree.c sqlite3BtreeSetPageSize(), but it
is still referenced from build.c.
The problem was introduced by Check-in [5dcfb0c9e4]: Make the TEMP file
On 01.12.2009 09:01, Dan Kennedy wrote:
Monday 30 of November 2009 12:29:10 Ralf Junker napisał(a):
I am passing various arguments to sqlite3_tokenizer_module.xCreate.
In case they are invalid, I would like to return an explaining
error message in addition to SQLITE_ERROR. I did not find
On 02.12.2009 20:00, Dan Kennedy wrote:
On Dec 2, 2009, at 3:07 PM, Ralf Junker wrote:
* Is it now intentionally possible to update FTS3 DOCIDs?
It is. The failing sqlite test case has been replaced.
Thanks you, Dan! I had already noticed!
Ralf
With the latest FTS3 changes, fts3b-4.9 no longer passes. This short SQL
emulates the test:
DROP TABLE IF EXISTS t4;
CREATE VIRTUAL TABLE t4 USING fts3(c);
INSERT INTO t4 (docid, c) VALUES (12, 'still testing');
UPDATE t4 SET docid = 14 WHERE docid = 12;
Note that SQLite 3.6.20
On 01.12.2009 09:01, Dan Kennedy wrote:
I don't think it is possible at the moment. Unfortunately.
Thanks for the clarification, Dan!
I observe that you are currently writing the official FTS3
documentation in preparation for the next release of SQLite.
Maybe you want to make tokenizer error
I have a compilation problem with line 22 in fts3Int.h:
#include sqlite3.h
According to http://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html,
file includes are used for system header files, which sqlite3.h is not
IMHO.
I tried to replace with
#include sqlite3.h
but this resulted in a
Compiling with SQLITE_OMIT_SUBQUERY, sqlite3ExprCodeIN() is compiled out
but at the same time still required at other places in expr.c.
As such, expr.c does not link well with SQLITE_OMIT_SUBQUERY defined.
After I wrapped the remaining references to sqlite3ExprCodeIN() by
#ifndef
On 01.12.2009 18:05, D. Richard Hipp wrote:
The key point to bare in mind here is that SQLITE_OMIT_SUBQUERY is
not a supported compile-time option. None of the major users of
SQLite make use of SQLITE_OMIT_SUBQUERY. We do not test it. And it
appears that it is broken in the current
On 01.12.2009 18:35, Jay A. Kreibich wrote:
Important Note: The SQLITE_OMIT_* compile-time options are
unsupported.
Oops! Thanks for focusing my eyes - they tend to skip introductions and
move right to the details.
Now having that read, let me point out that in spite of the statement
the
I am passing various arguments to sqlite3_tokenizer_module.xCreate. In case
they are invalid, I would like to return an explaining error message in
addition to SQLITE_ERROR. I did not find a way to do this. Is it at all
possible?
Thanks, Ralf
___
I am passing various arguments to sqlite3_tokenizer_module.xCreate. In case
they are invalid, I would like to return an explaining error message in
addition to SQLITE_ERROR. I did not find a way to do this. Is it at all
possible?
Thanks, Ralf
___
On 30.11.2009 20:33, Grzegorz Wierzchowski wrote:
Monday 30 of November 2009 12:29:10 Ralf Junker napisał(a):
I am passing various arguments to sqlite3_tokenizer_module.xCreate. In case
they are invalid, I would like to return an explaining error message in
addition to SQLITE_ERROR. I did
My memory manager reports that the SQL below results in memory being reused
after it has already been freed when it is RUN FOR A SECOND TIME on the same
database connection.
Psydocode (I do not run C):
sqlite3_initialize;
sqlite3_open(DB_FILE_NAME, DB);
sqlite3_exec(DB, SQL, NULL, NULL,
At 14:04 29.09.2009, Dan Kennedy wrote:
On Sep 29, 2009, at 4:30 PM, Ralf Junker wrote:
My memory manager reports that the SQL below results in memory being
reused after it has already been freed when it is RUN FOR A SECOND
TIME on the same database connection.
Hi Ralf,
Thanks
At 14:04 29.09.2009, Dan Kennedy wrote:
On Sep 29, 2009, at 4:30 PM, Ralf Junker wrote:
My memory manager reports that the SQL below results in memory being
reused after it has already been freed when it is RUN FOR A SECOND
TIME on the same database connection.
Hi Ralf,
Thanks
At 15:37 28.05.2009, D. Richard Hipp wrote:
Have you tried these two queries on other SQL database engines besides
SQLite? What do PostgreSQL and MySQL make of them?
I could now run the queries on Oracle Database 10g Express Edition Release
10.2.0.1.0.
Prepare the table:
create table t
Hello!
Up to version 3.5.3, SQLite would happily execute this SQL without complaints:
drop table if exists t;
create table t (c);
select
(select count() from t t_inner
group by t_outer.c)
from t t_outer;
This behaviour changed in version 3.5.4. From then on, SQLite issues an
At 13:27 28.05.2009, D. Richard Hipp wrote:
On May 28, 2009, at 7:01 AM, Ralf Junker wrote:
Hello!
Up to version 3.5.3, SQLite would happily execute this SQL without
complaints:
drop table if exists t;
create table t (c);
select
(select count() from t t_inner
group
At 13:27 28.05.2009, D. Richard Hipp wrote:
On May 28, 2009, at 7:01 AM, Ralf Junker wrote:
Hello!
Up to version 3.5.3, SQLite would happily execute this SQL without
complaints:
drop table if exists t;
create table t (c);
select
(select count() from t t_inner
group
At 15:37 28.05.2009, D. Richard Hipp wrote:
Have you tried these two queries on other SQL database engines besides
SQLite? What do PostgreSQL and MySQL make of them?
MySQL (5.0.21) reports no erros on either of both queries:
select
(select count(*) from t t_inner
group by
Hello!
Given this SQL:
drop table if exists t;
create table t (c);
select *
from t as ta
where t.c = ta.c;
SQLite3 chokes with the following error:
SQL error near line 5: no such column: t.c
Question:
Is this the expected behaviour? I know that the where clause does not
At 17:33 27.05.2009, D. Richard Hipp wrote:
On May 27, 2009, at 11:26 AM, Ralf Junker wrote:
Hello!
Given this SQL:
drop table if exists t;
create table t (c);
select *
from t as ta
where t.c = ta.c;
SQLite3 chokes with the following error:
SQL error near line 5
Confirmed and created ticket http://www.sqlite.org/cvstrac/tktview?tn=3841.
Ralf
At 03:10 07.05.2009, Steve Bauer wrote:
The following example demonstrates what seems to be a bug in group_concat.
With the latest version of CVS:
CREATE TABLE example (id INTEGER, x TEXT);
CREATE TABLE table2
At 15:37 20.04.2009, D. Richard Hipp wrote:
Ticket #3811 has been addressed by enhancing the documentation to
explain that journal_mode changes are only guaranteed to work if they
occur prior to the first transaction. Whether or not a journal_mode
change works after the start of the first
I experience some strange behaviour with SAVEPOINT in combination with
locking_mode=exclusive. Below is a script which I assembled from savepoint.text
13.1 to 13.4. Those tests run OK in normal locking mode, but fail in exclusive
locking more.
To reproduce, run the script below on a NEW and
Roger Binns wrote:
when a named constraint is violated, the name of the constraint which
actually failed is not included in the error message.
There has been a ticket about this for over 3 years, and also includes a
patch to fix it:
http://www.sqlite.org/cvstrac/tktview?tn=1648
Thanks,
BareFeet wrote:
See a comparison of several GUI SQLite tools here:
http://www.tandb.com.au/sqlite/compare/?ml
SQLiteSpy is missing from the list. It is available from
http://www.yunqa.de
SQLiteSpy is a Unicode SQLite3 database browser GUI for Win32. Features include:
* Database at a Glance
Hi,
when a named constraint is violated, the name of the constraint which actually
failed is not included in the error message.
Example 1:
create table con (
a text constraint must_not_be_null not null);
insert into con values (null);
Returns error con.a may not be null.
Example 2:
RB Smissaert wrote:
What SQLite version produced the file World.db3?
I am not 100% sure about the exact SQLite version which I used to create the
original World.db3, but I am VACUUMing it regularly to bring it up to date with
recent versions. So I expect it should be some version after 3.6.8.
Markus Hoenicka wrote:
If there's a way to find out at runtime that a column has been defined as
INTEGER PRIMARY KEY instead of as INTEGER, all is well and I'll be able to fix
the sqlite driver accordingly.
pragma table_info(table);
In SQLite, this SQL returns all columns defined for table
Shawn Wilsher wrote:
I seem to have found a crash that is 100% reproducible in SQLite 3.6.5. I'm
managed to make a reduced test case in a C file that can be found here:
http://files.shawnwilsher.com/2008/11/12/test.c
I could reproduce the problem and opened this ticket to make sure it does
Is there any
reliable method to determine the minimum page-cache allocation size
needed for a given page_size?
sqlite3_status(SQLITE_STATUS_PAGECACHE_SIZE, ...)
Unfortunately, there is extra overhead involved which is not handled by the
page cache but is allocated by malloc() if I
I am running the rtree module against an SQLite build which has
lots of functionality SQLITE_OMIT_...ed.
Can you be more specific? Exactly which SQLITE_OMIT symbols
are defined?
Sure. Here is the list:
SQLITE_OMIT_ALTERTABLE
SQLITE_OMIT_ANALYZE
SQLITE_OMIT_ATTACH
I am running the rtree module against an SQLite build which has lots of
functionality SQLITE_OMIT_...ed.
Surprisingly, I receive strange errors like SQLITE_NOMEM for simple statements
like
CREATE VIRTUAL TABLE t6 USING rtree(ii, x1, x2);
or
SELECT ii FROM t6 WHERE x12;
Question: Does
Steve Friedman wrote:
When trying to build sqlite (latest cvs update) with the following:
../sqlite-latest/configure --disable-threadsafe --enable-tempstore=always \
--disable-tcl --enable-extensions \
CFLAGS=-g -O3 -DSQLITE_ENABLE_RTREE=1 \
-DTEMP_STORE=2
Hello Jens Miltner,
However, I'd still like to know whether the new behavior of returning
the DISTINCT results in 'arbitrary' order is expected.
Unless ORDER BY is specified, the result of any SELECT is by definition
undefined. This undefined sort order has changed between previous versions
Darren Duncan wrote:
Ralf Junker wrote:
Can you suggest an alternative to a single reserved name to represent the
column which uniquely identifies a database record under any and all
circumstances?
Yes, change the interface to RowID into a routine call rather than a column
name; eg use RowID
Bradley A. Town wrote:
Ralf Junker wrote:
This alerts me to a potential danger for SQLite managers which must rely on
some means to retrieve THE RowID which uniquely identifies a record for
in-grid table editing. If the RowID name can be hijacked by other columns
and given another purpose
Federico Granata wrote:
have you seen here http://www.sqlite.org/autoinc.html ?
Yes, I did. This documentation actually made me realize that the problem is not
an implementation flaw but a design error, IMO. See my other answer in this
thread for more rationale.
Ralf
Darren Duncan wrote:
I think the real problem here is that SQL allows you to have non-distinct
rows in a table, when all rows should be distinct.
SQLite's implicit RowID does not allow non-distinct values (except for NULL,
but this is documented behavior and only maintained for backwards
Correcting myself:
This should NOT happen as SQLite usually rejects duplicate rowids with a
constraint error.
This should happen as SQLite usually rejects duplicate rowids with a
constraint error.
___
sqlite-users mailing list
I looked at the database attached to the ticked and noticed that the table
contains NULL rowids as well duplicate rowids. This should happen as SQLite
usually rejects duplicate rowids with a constraint error.
When I run this query:
select rowid, count() from ndxparamvalues_localizedstring
This should NOT happen as SQLite usually rejects duplicate rowids with a
constraint error.
For this table, the badly-named column RowID is actually a text field
that's allowed to be null, not a primary key.
-- Describe NDXPARAMVALUES_LOCALIZEDSTRING
CREATE TABLE
Drat. It doesn't look like there's a way to see what's already been
bound to a statement either, correct?
See this thread for a previous disuccsion of the problem:
http://www.mail-archive.com/sqlite-users@sqlite.org/msg28610.html
Ralf
___
In PERSIST mode, you have two files associated with your database
instead of one. Whenever you move, copy, or rename the database file
you *must* also move, copy or rename the journal file to prevent
database corruption.
The persistent journal file uses disk space that might otherwise
1 - 100 of 227 matches
Mail list logo
