Hi, yy_destructor function can not suppress warning about unused
%extra_argument variable. My yy_destructor function that Lemon generated
like this:
```
static void yy_destructor(
yyParser *yypParser,/* The parser */
YYCODETYPE yymajor, /* Type code for object to destroy */
On 1/22/15, Tang Tianyong tan...@gmail.com wrote:
Hi, yy_destructor function can not suppress warning about unused
%extra_argument variable.
Sure it can. Just add code to one of your destructors that references
the %extra_argument variable. It doesn't have to actually do anything
with the
On 1/7/15, The Responsa Project gr.respo...@biu.ac.il wrote:
To Whom it amy concern
I am trying to use SQLITE and the like statement with wildcards and hebrew
when I put in an english string it works correctly, such as
Select * from dbname where colname like '%123%'
I will get all the
To Whom it amy concern
I am trying to use SQLITE and the like statement with wildcards and hebrew
when I put in an english string it works correctly, such as
Select * from dbname where colname like '%123%'
I will get all the entries from that column that contain 123 anywhere in the
column.
On 2015/01/07 12:13, The Responsa Project wrote:
To Whom it amy concern
I am trying to use SQLITE and the like statement with wildcards and hebrew
when I put in an english string it works correctly, such as
Select * from dbname where colname like '%123%'
I will get all the entries from
How about to use dynamic binding?
For example, is your SQL(SELECT * from dbname where colname like '%אב%'),
use '?' instead of 'אב'.
In my guess, 'אב' can have same ASCII code of wildcard(%).
Full SQL can be as like as follows.
SELECT * from dbname where colname like '%?%'
To do this, you need
Hello All,
Page: https://www.sqlite.org/src/wiki?name=Bug+Reports
I recommend this change:
what the problem is.
what the problem was.
Reason: Rest of discussion is in past tense.
There were also numerous duplicates.
There were also numerous duplicate bug reports.
Reason: more complete
CREATE TABLE IF NOT EXISTS test (id INTEGER PRIMARY KEY AUTOINCREMENT,
temp text UNIQUE NOT NULL);
works OK
CREATE TABLE IF NOT EXISTS test (id INT PRIMARY KEY AUTOINCREMENT,
temp text UNIQUE NOT NULL);
gives error
AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY
Paul
On 11/16/2014 10:51 AM, Paul Sanderson wrote:
AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY
No it's not a bug. AUTOINCREMENT is only allowed on INTEGER PRIMARY KEY.
Which part of the error message do you find unclear?
For details, see http://www.sqlite.org/autoinc.html
You are supposing that INT PRIMARY KEY == INTEGER PRIMARY KEY. Which,
clearly, is not true.
http://stackoverflow.com/questions/20289410/difference-between-int-primary-key-and-integer-primary-key-sqlite
see this link for more on the subject.
2014-11-16 13:56 GMT-02:00 Igor Tandetnik
Thanks for the link Bernard
Paul
www.sandersonforensics.com
skype: r3scue193
twitter: @sandersonforens
Tel +44 (0)1326 572786
http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit
-Forensic Toolkit for SQLite
http://sandersonforensics.com/forum/content.php?168-Reconnoitre -
Hi,
I have using Sqlite for my small embedded projects for quite a while.
Recently we found a condition where is simple select all does not operate
properly.
Problem is incorrect journal file, which is created on system reboot.
Reproduce this condition relativity simple:
step 1: we open db
On 6 Nov 2014, at 3:13am, Andrei Yakimov anj...@gmail.com wrote:
Problem is incorrect journal file, which is created on system reboot.
Reproduce this condition relativity simple:
step 1: we open db
step 2: write/update something to db.
step 3: switch journal to memory
step 4:
On 6/10/2014 18:35, Clemens Ladisch wrote:
John wrote:
On 5/10/2014 19:59, Clemens Ladisch wrote:
The documentation http://www.sqlite.org/lang_datefunc.html says:
| These functions only work for dates between -01-01 00:00:00 and
| -12-31 23:59:59. For dates outside that range, the
John wrote:
On 5/10/2014 19:59, Clemens Ladisch wrote:
The documentation http://www.sqlite.org/lang_datefunc.html says:
| These functions only work for dates between -01-01 00:00:00 and
| -12-31 23:59:59. For dates outside that range, the results of
| these functions are undefined.
... group by statement.
Exchanging the sqlite.dll with a newer version, I get the following output:
sqlite_version= 3.8.6
[(1, 'd1', 100), (2, 'd1', 99), (3, 'd1', 98), (4, 'd2', 101), (5, 'd2', 102)]
[(3, 'd1', 98), (4, 'd2', 101)]
^^^
Question: Did I encounter a bug in the sqlite
Hi Christoph,
the id column does not appear in an aggregate function and also not in
group by.
Your statement uses 'GROUP BY Name' and so returns exactly one row per
name. If there are several rows with the same name, the ID of your
result is from one of these rows. The appropriate
There is an issue that if entry is selected in Table view then editing in
Query view and clicking delete key then it doesn't delete query but asks to
delete database entry which is not expected behavior.
___
sqlite-users mailing list
On Wed, Jul 30, 2014 at 8:53 AM, Oto _ oto...@gmail.com wrote:
There is an issue that if entry is selected in Table view then editing in
Query view and clicking delete key then it doesn't delete query but asks to
delete database entry which is not expected behavior.
It sounds as if you are
-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]
On Behalf Of Oto _
Sent: Wednesday, July 30, 2014 8:53 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] Sqlite querie delete bug
There is an issue that if entry is selected in Table view then editing in Query
view and clicking delete
Hello, SQLite team,
I would like to report a bug in the Windows Phone version of SQLite, that is
already present for three releases in the row. The problem arises quite
randomly, when SQLite refuses to insert or update some items into database and
throws the following error: SQL logic error
Sorry for another mail, but I forgot to mention, that the bug seems to arise
only in transaction. When the items are inserted individually, it seems to be
working correctly (although I can’t confirm it 100 %).
Hello, SQLite team,
I would like to report a bug in the Windows Phone version
On 19 Feb 2014, at 5:06am, Martin Zikmund martinzikm...@live.com wrote:
SQL logic error or missing database
The two usual causes of this under WinMob are both related to permissions and
privileges. The folder the database file is stored in may be protected against
the app opening the
Have you activated the error and warning log to see if it gives you any
further diagnostics?
http://www.sqlite.org/errlog.html
On Wed, Feb 19, 2014 at 12:06 AM, Martin Zikmund martinzikm...@live.comwrote:
Hello, SQLite team,
I would like to report a bug in the Windows Phone version of
Hi,
I am currently using sqlite3 version:
3.8.1 2013-10-17 12:57:35 c78be6d786c19073b3a6730dfe3fb1be54f5657a
I found an edge case bug in the sqlite3 shell when importing csv data with
fields containing embedded quotes, CRs and LFs:
When a field contains an embedded quote, and that embedded
Thanks for the test case. Fixed at
http://www.sqlite.org/src/info/5e239ecda0
On Wed, Dec 11, 2013 at 6:37 AM, Lindsay Lawrence thinknl...@gmail.comwrote:
Hi,
I am currently using sqlite3 version:
3.8.1 2013-10-17 12:57:35 c78be6d786c19073b3a6730dfe3fb1be54f5657a
I found an edge case bug
Don't ask me what use case made me notice this, but the
http://www.sqlite.org/lang_corefunc.html documentation for abs(), as of 12:29PM
EDT on 10/26/2013, is only about 99.89157978275145% accurate.
If X is the integer -9223372036854775807 then abs(X) throws an integer
overflow
On Sat, Oct 26, 2013 at 12:30 PM, George Collins george.coll...@outlook.com
wrote:
If X is the integer -9223372036854775807 then abs(X) throws an integer
overflow error since there is no equivalent positive 64-bit two complement
value.
It's off by one: X is actually -9223372036854775808.
I have found that the following command in my opinion returns an
incorrect exit code:
eric@sirius:~/src/sqlite-amalgamation-3071602$ ./sqlite3 appl.db .quit
eric@sirius:~/src/sqlite-amalgamation-3071602$ echo $?
2
This should (in my opinion) return 0 for success instead of 2. In
interactive
On 12/21/2012 05:18 PM, Dan Kennedy wrote:
Thanks. I think it's this:
http://www.sqlite.org/src/info/0cfd98ee20
Dan.
You are right. I have been re-reading our mail thread and this is
exactly what happens. I have build a SQLite
version from the latest version in the archive (3.7.16) and
On 12/21/2012 05:18 PM, Dan Kennedy wrote:
Thanks. I think it's this:
http://www.sqlite.org/src/info/0cfd98ee20
Dan.
Thanks. I have looked into ticket, but we also see this problem when the
backup is written and read by the
same SQLite version (3.7.5).
I have recreated a backup using the
On 01/02/2013 03:27 PM, Marco ten Thije wrote:
On 12/21/2012 05:18 PM, Dan Kennedy wrote:
Thanks. I think it's this:
http://www.sqlite.org/src/info/0cfd98ee20
Dan.
Thanks. I have looked into ticket, but we also see this problem when the
backup is written and read by the
same SQLite version
On 01/02/2013 10:04 AM, Dan Kennedy wrote:
What series of commands did you pass to 3.7.5 to create
this file?
This file was copied from an existing product which uses QT 4.7
libraries to populate the database. I cannot
reproduce the exact commands which resulted in this file, because it is
On 01/02/2013 11:03 AM, Marco ten Thije wrote:
On 01/02/2013 10:04 AM, Dan Kennedy wrote:
What series of commands did you pass to 3.7.5 to create
this file?
This file was copied from an existing product which uses QT 4.7
libraries to populate the database. I cannot
reproduce the exact
Hello,
We are facing a problem with the '.backup' command using the SQLite
command line interface. The resulting backup-database seems to be corrupt.
We ran into this problem on a ARM9 platform using SQLite 3.7.5, but it
can also be reproduced on the latest 3.7.15.1 version on Intel.
I
Can you please try running pragma integrity_check; on the original
database? That will give an indication of whether the original database
has any data corruption.
On Fri, Dec 21, 2012 at 4:13 AM, Marco ten Thije
marco.tenth...@usetechnology.nl wrote:
Hello,
We are facing a problem with
It returns 'ok':
./sqlite3 energy.sqlite
SQLite version 3.7.15.1 2012-12-19 20:39:10
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite pragma integrity_check;
ok
sqlite
So, the original database looks ok.
I have compared the two databases (original and backup) and
On 12/21/2012 08:46 PM, Marco ten Thije wrote:
It returns 'ok':
./sqlite3 energy.sqlite
SQLite version 3.7.15.1 2012-12-19 20:39:10
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite pragma integrity_check;
ok
sqlite
So, the original database looks ok.
I have
What is the size of the two database files?
The size of both files is 160768 bytes.
Also, can we have the first 6 lines of each hex dump
(i.e. enough to see the first 100 bytes)?
The first bytes of the original database:
000 5153 694c 6574 6620 726f 616d 2074 0033
010 0004 0101
On 12/21/2012 10:54 PM, Marco ten Thije wrote:
What is the size of the two database files?
The size of both files is 160768 bytes.
Also, can we have the first 6 lines of each hex dump
(i.e. enough to see the first 100 bytes)?
The first bytes of the original database:
000 5153 694c
The documentation (http://sqlite.org/tclsqlite.html) states:
The *sqlite3* command is used as follows:
*sqlite3* /dbcmd database-name/
However, the following shows up in the console:
$ tclsh
% package require sqlite3
3.7.12
% sqlite3
wrong # args: should be sqlite3
SQLite version 4.0.0 2012-07-07 12:21:48
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite create table t(a);
sqlite insert into t values(123);
sqlite insert into t values(123.0);
sqlite insert into t values(12323);
sqlite insert into t values(12323.0);
sqlite select *
On 10/07/2012 9:58 AM, bardzotajneko...@interia.pl wrote:
SQLite version 4.0.0 2012-07-07 12:21:48
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite create table t(a);
sqlite insert into t values(123);
sqlite insert into t values(123.0);
sqlite insert into t
On 7/10/2012 11:24 AM, Ryan Johnson wrote:
On 10/07/2012 9:58 AM,
bardzotajneko...@interia.pl wrote:
SQLite version 4.0.0 2012-07-07 12:21:48
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite create table t(a);
sqlite insert into t values(123);
sqlite insert into t
On Tue, Jul 10, 2012 at 11:33 AM, Igor Tandetnik itandet...@mvps.orgwrote:
On 7/10/2012 11:24 AM, Ryan Johnson wrote:
On 10/07/2012 9:58 AM,
bardzotajneko...@interia.pl wrote:
SQLite version 4.0.0 2012-07-07 12:21:48
Enter .help for instructions
Enter SQL statements terminated with a ;
On 7/10/2012 11:44 AM, Richard Hipp wrote:
SQLite4 is still using double internally for floating point
computations. (Yes, there are plans to change that but it has not happened
yet.) The bug above is due to rounding errors in the doubles, specifically
rounding errors that occur when doing the
On Tue, Jul 10, 2012 at 11:54 AM, Igor Tandetnik itandet...@mvps.orgwrote:
On 7/10/2012 11:44 AM, Richard Hipp wrote:
SQLite4 is still using double internally for floating point
computations. (Yes, there are plans to change that but it has not
happened
yet.) The bug above is due to
I looked into the problem more tonight and found all of the references
to the omitted functions were from the auto-generated parser. I looked
at the parser source and it was checking for omits in all the right
places so the functions should have have been referenced. I checked the
Makefile and
: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Jens Frederich [jfreder...@gmail.com]
Sent: Tuesday, December 27, 2011 1:59 AM
To: sqlite-users@sqlite.org
Subject: EXT :[sqlite] [shell] utf-8 bug
Hi all,
I believe there is a bug in shell tool on Windows. I've tried
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org]
on behalf of Jens Frederich [jfreder...@gmail.com]
Sent: Tuesday, December 27, 2011 1:59 AM
To: sqlite-users@sqlite.org
Subject: EXT :[sqlite] [shell] utf-8 bug
Hi all,
I believe there is a bug in shell tool
On Tue, Dec 27, 2011 at 12:44 PM, Jens Frederich jfreder...@gmail.com wrote:
The sqlite3 command line app doesn't write the string correctly to the
database file. It uses the terminal (cmd) encoding instead the 'PRAGMA
encoding' statement.
None of the SQLite3 code converts between encodings
On 12/27/11, Jens Frederich jfreder...@gmail.com wrote:
The sqlite3 command line app doesn't write the string correctly to the
database file. It uses the terminal (cmd) encoding instead the 'PRAGMA
encoding' statement.
chcp 65001 ...may not be a reliable avenue:
Thank you! What a mess...
On Tue, Dec 27, 2011 at 9:00 PM, Kevin Benson kevin.m.ben...@gmail.comwrote:
On 12/27/11, Jens Frederich jfreder...@gmail.com wrote:
The sqlite3 command line app doesn't write the string correctly to the
database file. It uses the terminal (cmd) encoding instead
Hi all,
I believe there is a bug in shell tool on Windows. I've tried to store
utf-8 encoded literals in my test db. Do the following to reproduce the
issue:
1. Open a Windows Console (cmd.exe)
2. chcp 65001 # change cmd.exe code page from 437(OEM) to utf-8
3. Run the shell
sqlite3.exe
On Wed, Dec 7, 2011 at 2:48 AM, Max Vlasov max.vla...@gmail.com wrote:
btw, could not find exact steps for getting trunk amalgamation.
Is it :
- get
http://www.sqlite.org/src/tarball/sqlite-latest-trunk.tar.gz?uuid=trunk
- extract on a unix-compatible machine
- ./configure
- make
Hi,
Noticed a strange regression after 3.7.7 (in 3.7.8 and inherited in 3.7.9)
I have a Russian morphology database and different queries working with it.
I narrowed it to the following case and populated with a couple of English
words (just to make sense)
The following database
CREATE TABLE
On 12/06/2011 03:28 PM, Max Vlasov wrote:
Hi,
Noticed a strange regression after 3.7.7 (in 3.7.8 and inherited in 3.7.9)
I have a Russian morphology database and different queries working with it.
I narrowed it to the following case and populated with a couple of English
words (just to make
On Tue, Dec 6, 2011 at 9:49 PM, Dan Kennedy danielk1...@gmail.com wrote:
On 12/06/2011 03:28 PM, Max Vlasov wrote:
Hi,
Noticed a strange regression after 3.7.7 (in 3.7.8 and inherited in 3.7.9)
There is a candidate fix for this in fossil now.
Dan, thanks
I checked the latest trunk
On Fri, Nov 18, 2011 at 05:30:20PM -0800, Yang Zhang scratched on the wall:
I just got bit by some peculiar behavior in sqlite where
id int primary key
is different from:
id integer primary key
In particular, sqlite will generate values for the latter but not the former:
Well, yes...
I just got bit by some peculiar behavior in sqlite where
id int primary key
is different from:
id integer primary key
In particular, sqlite will generate values for the latter but not the former:
sqlite create table a (a integer primary key, b integer);sqlite
insert into a (b) values (0);sqlite
-users-
boun...@sqlite.org] On Behalf Of Yang Zhang
Sent: Friday, November 18, 2011 6:30 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] Is this a bug? Can't tell from docs
I just got bit by some peculiar behavior in sqlite where
id int primary key
is different from:
id integer
Yuriy Kaminskiy wrote:
Yuriy Kaminskiy wrote:
David wrote:
Simon L wrote 2011-10-25 06:20:
To reproduce this problem, enter the following 5 SQL statements at the
SQLite command line.
create table X(id INTEGER primary key ON CONFLICT REPLACE);
create table Y(id INTEGER primary key ON
Yuriy Kaminskiy wrote:
David wrote:
Simon L wrote 2011-10-25 06:20:
To reproduce this problem, enter the following 5 SQL statements at the
SQLite command line.
create table X(id INTEGER primary key ON CONFLICT REPLACE);
create table Y(id INTEGER primary key ON CONFLICT REPLACE);
insert
into Y select * from X;
insert into Y select * from X;
When I tried to run the last SQL statement twice, SQLite produced the
following error message.
Error: PRIMARY KEY must be unique
Is this a bug? Please advise. Thank you.
___
sqlite-users
Thanks for fixing that so quickly. Looking forward to a new release.
Patrick Earl
On Sat, Jul 9, 2011 at 2:39 PM, Joe Mistachkin sql...@mistachkin.com wrote:
Patrick Earl wrote:
System.Resources.MissingManifestResourceException was unhandled
Message=Could not find any resources
First I wanted to say that I was so excited to see the 1.0.74 release
with .NET 4, zip files, and SQLite 3.7.7. I've been waiting for .NET
4 support for a long while. Thanks so much. :)
Unfortunately, I was unable to upgrade from 1.0.66 because of the
following problem.
Using this code
Patrick Earl wrote:
System.Resources.MissingManifestResourceException was unhandled
Message=Could not find any resources appropriate for the specified
culture or the neutral culture. Make sure
System.Data.SQLite.SR.resources was correctly embedded or linked
into assembly
Hello there!
I found a strange behavior while doing a
select with a sub select that has a where clause with a value (here
'a') which is the same as a column id:
What am I missing here ?
SQLite version 3.7.5
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite .mode
On Tue, Jun 28, 2011 at 8:42 PM, thilo th...@nispuk.com wrote:
sqlite select (select v from t1 where n=a) wrong,* from a1;
use SINGLE quotes, not double quotes.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
___
sqlite-users
string literals are enclose in single quotes not double quotes
select (select v from t1 where n='a') wrong,* from a1;
On 6/28/2011 11:42 AM, thilo wrote:
select (select v from t1 where n=a) wrong,* from a1;
___
sqlite-users mailing list
...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of thilo [th...@nispuk.com]
Sent: Tuesday, June 28, 2011 1:42 PM
To: General Discussion of SQLite Database
Subject: EXT :[sqlite] Is this a BUG or am I wrong ? sub-select returns nothing
when column id matches the inner query
Hello there!
I
On 6/28/2011 8:45 PM, Stephan Beal wrote:
On Tue, Jun 28, 2011 at 8:42 PM, thilo th...@nispuk.com wrote:
sqlite select (select v from t1 where n=a) wrong,* from a1;
use SINGLE quotes, not double quotes.
bummer, Thanks a lot
thilo
--
Dipl. Ing. Thilo Jeremias
Zur Rabenwiese 14
27239
On Tue, Jun 28, 2011 at 8:50 PM, thilo th...@nispuk.com wrote:
use SINGLE quotes, not double quotes.
bummer, Thanks a lot
i PROMISE that you won't find such an obvious bug in sqlite3 ;).
sqlite uses single quotes because that's what ANSI SQL specifies. MySQL uses
(or can use) double quotes
Sqlite 3.7.5. Possible NATURAL JOIN bug.
I have a ~100 MB database which gives me odd results when running two similar
queries. I'm currently trying to create a minimal test case, but the error
seems to go away when I try to narrow it down.
In short, the queries look like this (scrambled :P
Igor Tandetnik wrote:
On 1/26/2011 6:39 PM, Eric Smith wrote:
busy handler not called on lock escalation
This behavior is by design. See
http://sqlite.org/c3ref/busy_handler.html
the part that talks about a deadlock.
Understood agreed.
This is a bug in the Tcl API documentation,
Hello!
I've found a bug in execution queries like this:
SELECT ... FROM table T JOIN table2 T2 ON T2.child=T.master
WHERE T2.attr in(SELECT value FROM table3 T3 JOIN (SELECT group, MAX(value)
FROM table4 T4 WHERE T4.date_value=T2.date_value GROUP BY group) G ON
G.group=T3.group)
Such queries
On Tue, Jan 18, 2011 at 12:07 PM, Vadim Smirnov vsmir...@ptsecurity.ruwrote:
Hello!
I've found a bug in execution queries like this:
SELECT ... FROM table T JOIN table2 T2 ON T2.child=T.master
WHERE T2.attr in(SELECT value FROM table3 T3 JOIN (SELECT group, MAX(value)
FROM table4 T4 WHERE
Thanks Martin,
Maybe the documentation could be extended:
The ltrim(X,Y) function returns a string formed by removing any and all
characters that appear in Y from the left side of X. If the Y argument
is omitted, ltrim(X) removes spaces from the left side of X.
to:
The ltrim(X,Y) function
Hi,
the following seems wrong to me:
bash-4.0# sqlite3
SQLite version 3.6.14.2
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite select ltrim(12300567,1230);
567
sqlite select ltrim(012300567,0123);
567
sqlite select ltrim(12300567,123);
00567
sqlite
Is the
Hi,
this is the expected behaviour.
See http://www.sqlite.org/lang_corefunc.html
The ltrim(X,Y) function returns a string formed by removing any and all
characters that appear in Y from the left side of X. If the Y argument
is omitted, ltrim(X) removes spaces from the left side of X.
The
On Thu, Dec 23, 2010 at 3:10 PM, Max Vlasov max.vla...@gmail.com wrote:
Hi,
I experimented with artificial power loss (using hd box) and 3.7.4 both
library and shell didn't restore the files to the initial state. 3.6.10
restores successfully.
This is a kind of repost, there wasn't any
Hi,
12/01/2011 12:27, Max Vlasov wrote:
On Thu, Dec 23, 2010 at 3:10 PM, Max Vlasovmax.vla...@gmail.com wrote:
Hi,
I experimented with artificial power loss (using hd box) and 3.7.4 both
library and shell didn't restore the files to the initial state. 3.6.10
restores successfully.
This
On Wed, Jan 12, 2011 at 5:27 AM, Max Vlasov max.vla...@gmail.com wrote:
On Thu, Dec 23, 2010 at 3:10 PM, Max Vlasov max.vla...@gmail.com wrote:
Hi,
I experimented with artificial power loss (using hd box) and 3.7.4 both
library and shell didn't restore the files to the initial state.
On Wed, Jan 12, 2011 at 3:48 PM, Richard Hipp d...@sqlite.org wrote:
On Wed, Jan 12, 2011 at 5:27 AM, Max Vlasov max.vla...@gmail.com wrote:
On Thu, Dec 23, 2010 at 3:10 PM, Max Vlasov max.vla...@gmail.com
wrote:
Hi,
I experimented with artificial power loss (using hd box) and 3.7.4
Hi,
I experimented with artificial power loss (using hd box) and 3.7.4 both
library and shell didn't restore the files to the initial state. 3.6.10
restores successfully. I don't know whether it's related the the contents of
the file, but here the db files:
On Thu, Dec 23, 2010 at 3:10 PM, Max Vlasov max.vla...@gmail.com wrote:
Hi,
I experimented with artificial power loss (using hd box) and 3.7.4 both
library and shell didn't restore the files to the initial state. 3.6.10
restores successfully. I don't know whether it's related the the contents
When I run the following piece of SQL in an empty database, I get a
no such table: main.table_e error on the second DROP TABLE
statement:
CREATE TABLE table_e (
eid TEXT PRIMARY KEY
);
CREATE TABLE table_t (
tid TEXT PRIMARY KEY,
value TEXT
);
CREATE TABLE table_b (
-- Foreign
[critical bug] sqlite3: col name bug on select statemnt
sqlite3 --version
3.7.3
this bug occures with count or sum .
c:\tmp sqlite3 test3.db
.header ON
-- bug
drop table t1;
drop table t2;
drop table t3;
CREATE TABLE t1 (col1
A user has provided us with a script that appears to result in SQLite
database corruption. The problem has existed in all versions of SQLite
going back to 3.6.16 in June of 2009. A bisect shows that the problem was
injected on 2009-06-17.
The problem appears to be associated with incremental
Hello SQLite Team,
We currently use sqlite 3.6.23. We have a big problem with characters with
accents or other special characters in path to database file, for example in
Czech Windows XP the Application Data folder is translated to Data
aplikací so if the accented 'í' is in path the
sqlite3_open[_v2] accepts all filenames in UTF-8 (although it doesn't
check for valid UTF-8 string). So CP_UTF8 cannot be changed anywhere.
OTOH maybe command line utility should have some logic of re-encoding
of command line parameter from terminal encoding to UTF-8. But I'm not
sure about that.
We currently use sqlite 3.6.23. We have a big problem with characters with
accents or other special characters in path to database file, for
example in
Czech Windows XP the Application Data folder is translated to Data
aplikací so if the accented 'í' is in path the sqlite3.exe writes that it
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe Deschamps wrote:
A much better solution is to use a MSYS terminal (installed by MinGW),
so you have UTF-8 command-line and data entry/display without
conversion. No need to patch anything.
No need for msys. You can make a
Just a note to share a problem I ran into recently: Compiling sqlite 3.6.22
with -arch ppc -Os on the llvm that ships with Xcode 3.2.1, the sqlite3AtoF
function appears to have an infinite loop. If you compile the sqlite3 command
line tool in this way, just executing select round(1234); will
Hello all,
I've run into an interesting situation; when duplicating parenthesis
around a 'in ()' subquery, only the first row is returned.
This is not my real-life query, but a test that replicates the problem.
Thanks,
Valerio
$ sqlite3 --version
3.6.16
prepare some dummy data:
create
Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Valerio Aimale
Sent: sábado, 19 de dezembro de 2009 00:23
To: sqlite-users@sqlite.org
Subject: [sqlite] is this a bug?
Hello all,
I've run into an interesting situation; when duplicating
On Fri, Dec 18, 2009 at 8:23 PM, Valerio Aimale vale...@aimale.com wrote:
Hello all,
I've run into an interesting situation; when duplicating parenthesis
around a 'in ()' subquery, only the first row is returned.
This is not my real-life query, but a test that replicates the problem.
:38
To: General Discussion of SQLite Database
Subject: Re: [sqlite] is this a bug?
On Fri, Dec 18, 2009 at 8:23 PM, Valerio Aimale vale...@aimale.com wrote:
Hello all,
I've run into an interesting situation; when duplicating parenthesis
around a 'in ()' subquery, only the first row is returned
On Fri, Dec 18, 2009 at 07:23:24PM -0700, Valerio Aimale scratched on the wall:
Hello all,
I've run into an interesting situation; when duplicating parenthesis
around a 'in ()' subquery, only the first row is returned.
Why only one value returned when parenthesis are duplicated?
Hi,
At 00:11 13/12/2009, you wrote:
Sir any ida how can value rounddown floor have done
if not possible i have make small code
i requard make function please say how can add
i send you my rounddown funtion
please
Cose Exmaple :
value=10.666
decimal=1
Create roundd{value,decimal){
if
1 - 100 of 196 matches
Mail list logo
