On Wed, May 22, 2013 at 7:53 PM, Stephan Beal wrote:
> make -f GNUmakefile.linux
libsqlite4.a(fts5func.o): In function `fts5Rank':
/home/user/db/build/sqlite4/src/fts5func.c:159: undefined reference to `log'
collect2: ld returned 1 exit status
make: *** [sqlite4] Error 1
_
On Wed, 22 May 2013 12:23:12 -0700
"Kevin Keigwin" wrote:
> What I don't understand is why the database is so forgiving of dates
> being saved, while the SQLiteDataAdapter isn't.
As Simon said, "SQLite doesn't have a DateTime type." As far as SQLite
is concerned, your datestring is a string, no
Simon Slavin wrote:
>
> Perhaps you might want to take the source code for the existing julian
> date function and modify it.
>
If the system in question is online, perhaps the following URL (or one
like it) could be fetched periodically and used to help synchronize said
custom extension:
On 5/22/2013 6:48 PM, Stephan Buchert wrote:
It seems that I failed to make the point clear:
On June 30, 2012 the 86401st second happened in the real world
I think you mean "a second was artificially added by some, but not all
or even most, people to some, but not all or even most, calendar
On 22 May 2013, at 11:48pm, Stephan Buchert wrote:
> However, Sqlite's julianday seems to have limitations because it returns
> NULL for times that fall in leap seconds (in addition, it is off by
> presently about 1 min from the Julian Day that is used in astronomy).
> Perhaps the reason is that
It seems that I failed to make the point clear:
On June 30, 2012 the 86401st second happened in the real world, it was
working time in parts of the US. In this second there were financial
transactions, photos were taken, sensors delivered data, etc etc, events
that users might want to insert into
On Wed, May 22, 2013 at 7:06 PM, wrote:
>
> (I think Fehmi diagnosed the problem, that you should not use the "sqlite3"
> command when you are already in the "sqlite3" program. This is about
> something completely different.)
>
> If you are using a recent version of Windows, you do not want to
(I think Fehmi diagnosed the problem, that you should not use the "sqlite3"
command when you are already in the "sqlite3" program. This is about something
completely different.)
If you are using a recent version of Windows, you do not want to be trying to
create your database in the c:\windo
Dear fellow SQLite afficionados,
Thanumalayan Sankaranarayana Pillai wrote:
"I expect it wouldn't be a problem with WAL"
Thé SQLite (not wanting, but cobsidering him at leat kind of) Force D. Richard
H. [who does not know Him don't read this message, you won;t understand enough
I'm afraid
On 5/22/2013 5:28 PM, Stephan Buchert wrote:
Sqlite's julianday in the leap second seems to be NULL:
sqlite> select julianday('2012-06-30T23:59:60')*86400;
So is julianday('foobar'). '2012-06-30T23:59:60' is simply not a
syntactically valid time string, per
http://www.sqlite.org/lang_datefun
Thank you, igor.
I've learned one more, today!
2013. 5. 22. 오후 10:20에 "Igor Tandetnik" 님이 작성:
> On 5/22/2013 12:53 AM, Yongil Jang wrote:
>
>> But, in case of using BETWEEN operator with "COLLATE nocase", it returns
>> unexpected result as follows.
>>
>> sqlite> select * from mytable where data be
Yes, the documentation gives there a hint that also the Sqlite time
functions have the usual problems with the leap seconds.
A specific example:
sqlite> select julianday('2012-06-30T23:59:59')*86400;
212207860799.0
The up to now most recent leap second then was from 2012-06-30T23:59:60
to 2012-0
On 22 May 2013, at 8:23pm, "Kevin Keigwin" wrote:
> And I've discovered the source of the problem by downloading the source code
> and debugging the SQLiteDataAdapter. I had created some test data through
> the GUI tool and entered a non-ISO8601 date string. Because SQLite is so
> forgiving wh
>Can you try the other stuff I wrote ? We don't yet have enough information
to figure out what's going wrong.
>Simon.
Sorry, Simon. I missed what else you wrote because it was embedded in my
original email text. My error.
And I've discovered the source of the problem by downloading the source
Yeah, the index maintenance is enormous, but it means that the select times are
fast. Medical info systems are usually pretty heavily oriented toward fast
read operations.
Our table here has a set of repeated substructures (8-column structures that we
have 6 of, with certain fields used on eac
> The time available in computers (smartphones etc) is normally UTC and a
> local time offset, which is sufficient for almost all times, but not
> quite all. On average every 18 months leap seconds are inserted. Events
> during these leap seconds cannot be unambiguously timestamped by a
> represen
I haven't had a table that large, but I have had big ones... the disadvantage
is the number of records you can scan in a single disk read, but an advantage
is that you don't have to take the time to join tables, especially when you
need to do it ALL THE TIME.
-Original Message-
From: sq
I was just thinking of that... if you have needs to dozens of covering indexes,
then the index maintenance anytime you modify the table must be enormous. It
makes me think you might be better off using triggers to maintain separate
tables with covered data instead of indexes. The only downside
On 22 May 2013, at 7:58pm, David de Regt wrote:
> if I have a 300 column table
I'm going to sound my customary note of caution here. Do you really have a 300
column table or is it several thinner tables which have the same primary key ?
Or do you really have a property list which should be
Correct. However, we have a pile of different uses on this table. I'm trying
to evaluate if we can move all covering index columns into the first 63, but
I'm not sure it's going to work, especially long term as we continue to grow
the data. We'll see...
In the medical industry I used to work
On May 22, 2013, at 8:58 PM, David de Regt wrote:
> Back to the trenches to rearchitect this…
Perhaps an opportunity to introduce bitmap indexes to SQLite… which would
render compound indexes a thing of the past for certain class of problems such
as yours...
http://en.wikipedia.org/wiki/Bitm
On Wed, May 22, 2013 at 3:01 PM, Marc L. Allen
wrote:
> I think there might be a disconnect.
>
> You can have a covering index on a 300 column table... it just can't cover
> any column past the 63rd (or 64th?).
>
63rd. The 64th bit is catch-all used to mean that some column past the
63rd is used
On 22 May 2013, at 7:59pm, Kevin Keigwin wrote:
> I understand.
Can you try the other stuff I wrote ? We don't yet have enough information to
figure out what's going wrong.
Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.
I think there might be a disconnect.
You can have a covering index on a 300 column table... it just can't cover any
column past the 63rd (or 64th?).
It's not perfect, but not as bad as not being able to have a covering index at
all.
At least, that's how I read some of the answers.
-Origin
>SQLite doesn't have a DateTime type. If you are using some sort of library
which does type testing and produces an error if the value is of >the wrong
type, it will always produce an error message when checking for DateTime.
>Simon.
I understand. As I said in my post, the underlying type of th
Hm. That's a wee bit of an issue for us, then. May want to stick that on the
limitations page... :)
It seems like covering indexes become increasingly useful the more columns you
have on a table. When I have a 4-column table, if my covering index uses 3
columns, that's not as big a read savi
On Wed, May 22, 2013 at 2:37 PM, David de Regt wrote:
> I'm experimenting with covering indices on one of our larger tables.
>
> *[many words expressing concern that SQLlite does not use covering
> indices on tables with more than 63 colums]...*
>
>
Your observations are correct. If a query uses
I'm experimenting with covering indices on one of our larger tables. I started
seeing really inconsistent behavior, and made the following sample setup code
that demonstrates it:
DROP TABLE IF EXISTS test;
CREATE TABLE test(
col01 integer,col02 integer,col03 integer,col04 integer,col05 integer
On 22 May 2013, at 5:47pm, "Kevin Keigwin" wrote:
> When our code tries to execute "SELECT * FROM ORDER by
> .id", I get the exception "String was not recognized as a valid
> DateTime".
Use your code to populate your database but don't worry about a SELECT command.
Download the sqlite3 shell
I've been given the task of creating an adapter for our software to read
existing SQLite/spatialite data tables. I am using the latest version of
SQLite.net, which I obtained from the precompiled x86 binaries for .NET 4.0.
When our code tries to execute "SELECT * FROM ORDER by
.id", I get the exc
On Wed, May 22, 2013 at 4:13 PM, Prashant Shah wrote:
> How can I compile sqlite4 ? Is there a amalgamation file available ?
>
Try:
make -f GNUmakefile.linux
or:
ln -s GNUmakefile.linux GNUmakefile
make
That "should" do it for you.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
On Wed, May 22, 2013 at 11:17 AM, Fehmi Noyan ISI wrote:
> Oh my gosh! you are in business man...
>
> You run the sqlite without any problems, don't you? Have a look at the
> step-by-step cmd.exe example below
> As other guys pointed out in their previous posts, you supposed to use
> "sqlite3 te
Regarding: Either way when I open the shell it gives me a sqlite> prompt,
not sqlite3>
Yes, I suspect Igor intended
sqlite>
But to his larger point, am I close to correct in replicating your error
below? I strongly suspect you're typing "sqlite3" when you are already
inside the
Hi,
Also, how do I build a .so file ?
Regards.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On Wed, May 22, 2013 at 10:16 AM, Sean Dzafovic wrote:
>
> I only downloaded 2 files. The Sqlite shell and the Sqlite .dll listed
> under precompiled binaries for windows on the download page. I did not
> compile anything. I moved the .dll to the system32 folder and tried to
> run the shell from
Oh my gosh! you are in business man...
You run the sqlite without any problems, don't you? Have a look at the
step-by-step cmd.exe example below
As other guys pointed out in their previous posts, you supposed to use "sqlite3
test.db" command from the Windows Command line. Not inside the sqlite s
On Wed, May 22, 2013 at 10:05 AM, Stephan Buchert wrote:
> 1) do nothing, or maybe just document more clearly, that the julianday
> in Sqlite, for date/time input in UTC, returns JD(UTC) in IAU
> terminology, which, for example, does give time differences (or nr of
> days elapsed since epoch) igno
On Wed, May 22, 2013 at 11:07 AM, Fehmi Noyan ISI wrote:
> I think it depends on how you compiled sqlite. I my case, it is dynamically
> linked to dll, so I do need the dll file (with a smaller exe size). However,
> a static link seems suites better the case for sqlite (how big can its file
> s
Hi,
How can I compile sqlite4 ? Is there a amalgamation file available ?
I tried downloading the fossil package :
$fossil clone http://www.sqlite.org/src4/sqlite4.fossil sqlite4
$ ./autogen.sh
configure.in: warning: missing AC_CHECK_FUNCS([fdatasync]) wanted by:
src/lsm_unix.c:181
configure.in:
On Wed, May 22, 2013 at 10:59 AM, wrote:
> The dll and exe should be sufficient to run sqlite.
>
> What version of sqlite are you using?
> sqlite3 --version
>
> Not sure about this, but may it be something related to user privilages?
When I start the shell i see
SQLite version 3.7.17 2013-05-20
I think it depends on how you compiled sqlite. I my case, it is dynamically
linked to dll, so I do need the dll file (with a smaller exe size). However, a
static link seems suites better the case for sqlite (how big can its file size
be!?)
From: Adam DeVita
T
Sqlite provides in its SQL the julianday function, which can serve as a
timestamp with a good resolution (millisecs, double precision
floating point numbers are used) and for times way back into the past
and far into the future. However, as presently implemented, the
function does not really retur
When you open the command prompt you will see something like this:
c:\PINTS>sqlite3.exe
SQLite version 3.6.10
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite>
The above clearly indicates version 3.6.10.
Others on the list will correct me if I am wrong, but the com
The dll and exe should be sufficient to run sqlite.
What version of sqlite are you using?
sqlite3 --version
Not sure about this, but may it be something related to user privilages?
On 22/05/2013, at 11:21 PM, Sean Dzafovic wrote:
> On Wed, May 22, 2013 at 10:30 AM, Igor Tandetnik wrote:
>> On
On Wed, May 22, 2013 at 10:30 AM, Igor Tandetnik wrote:
> On 5/22/2013 8:58 AM, Sean Dzafovic wrote:
>>
>> I downloaded the shell and the dll from the sqlite.org site. I put the
>> .dll in the windows/system32 folder. However, when I try to create a
>> test db using the command "sqlite3 test.db" a
No, I have reported everything. The only thing I missed might be that it's
not "5 seconds" always, but rather the configurable commit interval of the
filesystem, which is by default 5 seconds in most desktop Linux distros.
I only read through the source code of test6.c, and misunderstood that
ftru
On 5/22/2013 8:58 AM, Sean Dzafovic wrote:
I downloaded the shell and the dll from the sqlite.org site. I put the
.dll in the windows/system32 folder. However, when I try to create a
test db using the command "sqlite3 test.db" as per the example, I get
"Error: near "sqlite3" :syntax error.
What
On Wed, May 22, 2013 at 10:06 AM, Fehmi Noyan ISI wrote:
> I do not have this issue with my sqlite 3.7.14 installation in Win7.
>
> Any more details?
Windows XP SP2.
Did I forget to download some files?
Sean
___
sqlite-users mailing list
sqlite-users@
On 5/22/2013 12:53 AM, Yongil Jang wrote:
But, in case of using BETWEEN operator with "COLLATE nocase", it returns
unexpected result as follows.
sqlite> select * from mytable where data between 'abc/' and 'ABC0' COLLATE
nocase;
Make it
where data COLLATE nocase between 'abc/' and 'ABC0'
The
I do not have this issue with my sqlite 3.7.14 installation in Win7.
Any more details?
From: Sean Dzafovic
To: sqlite-users@sqlite.org
Sent: Wednesday, May 22, 2013 10:28 PM
Subject: [sqlite] Getting Started with Sqlite
I downloaded the shell and the dll fr
On Wed, May 22, 2013 at 8:31 AM, thanumalayan mad wrote:
>
> Also, not to spam, but it would be great if you could answer these
> questions for my research (you might send me a reply directly without going
> through the mailing list): [a] Was it always understood that unlink() and
> ftruncate() ar
I downloaded the shell and the dll from the sqlite.org site. I put the
.dll in the windows/system32 folder. However, when I try to create a
test db using the command "sqlite3 test.db" as per the example, I get
"Error: near "sqlite3" :syntax error.
What am I doing wrong?
Thanks,
Sean Dzafovic
Thank you very much. It works.
Vielen Dank,
Patrik
On 05/22/2013 12:22 PM, Hick Gunter wrote:
>
> DELETE FROM history WHERE 2 < (SELECT count() FROM history n WHERE
> n.id=history.id and n.lastactivity > history.lastactivity);
>
> -Ursprüngliche Nachricht-
> Von: Patrik Nilsson [mailto
On Sat, May 18, 2013 at 4:41 AM, thanumalayan mad wrote:
>
> Expected result: You always find that the transaction had been executed.
> Observed result: You sometimes find that the transaction did not execute.
>
The core team has discussed this. In order to avoid a substantial
performance hit ag
DELETE FROM history WHERE 2 < (SELECT count() FROM history n WHERE
n.id=history.id and n.lastactivity > history.lastactivity);
-Ursprüngliche Nachricht-
Von: Patrik Nilsson [mailto:nipatriknils...@gmail.com]
Gesendet: Mittwoch, 22. Mai 2013 10:48
An: General Discussion of SQLite Database
Hi All,
I can't figure out how to delete with offset using groups.
Imagine I have a table
create table history(id integer, lastactivity datetime default
(datetime('now')))
and I insert values as
insert into history (id) values (1)
A resulting table might look
1|2013-05-22 07:50:05
1|2013-05-2
56 matches
Mail list logo
