L.S.
I've noticed that on a platform for which SQLITE_MIXED_ENDIAN_64BIT_FLOAT
needs to be defined, Sqlite exposes itself to any difference between the
floating point implementation in Sqlite as opposed to the one used by the
underlying platform. To me this seems like something that needs to be
"ir. F.T.M. van Vugt bc." <[EMAIL PROTECTED]> wrote:
>
> I'm unsure how D. Richard Hipp would prefer to handle this, I reported these
> findings directly to him before posting here, but got no response ;(
>
My response was http://www.sqlite.org/cvstrac/chngview?cn=4339 :-)
--
D. Richard Hipp
Regarding: "Is there any other method where i can store the sorted
results and use that whenever needed instead f doing order by each
time."
You're using an index on the "Albums" column, right? If not, that will
make a tremendous difference.
This message has been scanned for viruses by MailC
> > I'm unsure how D. Richard Hipp would prefer to handle this, I reported
> > these findings directly to him before posting here, but got no response
> > ;(
>
> My response was http://www.sqlite.org/cvstrac/chngview?cn=4339 :-)
That serves me for not paying close attention to the changes in cvs
Whats the procedure and rules for merging two tables?
I have table #1, with a possible 86 thousand entries a day. an embedded
application is storing sensor data.
I have table #2, with a possible 50 entries a day.
Both tables have a date/time field.
Do I need duplicate columns in both table
I have an application that is inserting a record every second. There
are thousands of periods from a few seconds to hours long where the data
in all the columns is identical thus causing hundreds of thousands of
duplicate rows.
Is there a way to set up the INSERT statement to allow the insert
On Tue, 04 Sep 2007 07:53:08 -0600, you wrote:
>I have an application that is inserting a record every second. There
>are thousands of periods from a few seconds to hours long where the data
>in all the columns is identical thus causing hundreds of thousands of
>duplicate rows.
>
>Is there a w
Kees Nuyt wrote:
On Tue, 04 Sep 2007 07:53:08 -0600, you wrote:
I have an application that is inserting a record every second. There
are thousands of periods from a few seconds to hours long where the data
in all the columns is identical thus causing hundreds of thousands of
duplicate row
Scott Derrick wrote:
I have an application that is inserting a record every second. There
are thousands of periods from a few seconds to hours long where the
data in all the columns is identical thus causing hundreds of
thousands of duplicate rows.
Is there a way to set up the INSERT stateme
On 9/3/07, Babu, Lokesh <[EMAIL PROTECTED]> wrote:
> One more question, As you said, Full text builds an index of data, so
> I hope you have done some memory analysis too, could you please tell
> me the memory usage based on your analysis.
That's really something that you'll wan to do with your sp
What is the difference between:
MYCOLUMN NUMERIC
Vs
MYCOLUMN INTEGER
Or does it really mean nothing,
I remember somewhere the default column type could be integer, after
that it defaults to whatever you insert.
But I was wondering... what would the preferred type be to
A:
Good Evening.
SCHEMA:
SOMECOLUMN TEXT
I use the API as always:
ColType := sqlite3_column_type(Pointer(FHandle), I);
This has always worked fine for me and type returned was SQLITE_TEXT
however lately I noticed that a particular table this is sometimes
returned to me as SQ
"Andre du Plessis" <[EMAIL PROTECTED]> wrote:
>
> I use the API as always:
>
> ColType := sqlite3_column_type(Pointer(FHandle), I);
>
> This has always worked fine for me and type returned was SQLITE_TEXT
>
If sqlite3_column_type() returns SQLITE_NULL when in fact
the column really contains a
On Tue, 04 Sep 2007 09:20:28 -0700, Gerry wrote:
>Kees Nuyt wrote:
>> On Tue, 04 Sep 2007 07:53:08 -0600, Scott wrote:
>>
>>> I have an application that is inserting a record every second. There
>>> are thousands of periods from a few seconds to hours long where the data
>>> in all the columns
Use sqlite3_step to read each row in sequence.
Babu, Lokesh wrote:
Dear all,
After doing some SELECT operation on a TABLE, say we get 100 result
items out of 1000 records, Is there any way where I can iterate
through this result set. i.e., Get N items out of 100, say get
previous 10, get next 1
These are regular floating point numbers, and behave accordingly.
Serena Lien wrote:
I have read some of the postings/faq about the difficulties with the round
function, when certain numbers do not have a finite representation in
binary, which SQLite uses. eg 9.95 is actually 9.9499...etc so tha
SQLite use the 'cursor' style like SQL Server / ORACLE in stored procedures:
you fetch in a unidirectional (forward only) way.
To achieve bi-directional support you must have to store the results in
memory as you fetch them (not so difficult to accomplish if you have enough
memory to do it, a bit
Hi all!
Tried upgrading to the 3.5.0 alpha from 3.4.2 using VS 2005 on XP. I
downloaded the ZIP with preprocessed C code.
Compiling SQLite to a .lib was no problem, but when linking it to an
.exe I got the following:
sqlite.lib(mutex_w32.obj) : error LNK2019: unresolved external symbol
_TryEnt
Did you trying linking against kernel32.dll/lib ?
http://msdn2.microsoft.com/en-us/library/ms686857.aspx
--- Daniel Önnerby <[EMAIL PROTECTED]> wrote:
> Tried upgrading to the 3.5.0 alpha from 3.4.2 using VS 2005 on XP. I
> downloaded the ZIP with preprocessed C code.
> Compiling SQLite to a .li
On 5/09/2007 6:18 AM, John Stanton wrote:
These are regular floating point numbers, and behave accordingly.
Utter nonsense. round(98926650.5, 1) -> 98926650.501 is a BUG.
98926650.5 is representable EXACTLY in "regular" floating point.
The round function should calculate a scale factor (10
=?ISO-8859-1?Q?Daniel_=D6nnerby?= <[EMAIL PROTECTED]> wrote:
> Hi all!
>
> Tried upgrading to the 3.5.0 alpha from 3.4.2 using VS 2005 on XP. I
> downloaded the ZIP with preprocessed C code.
> Compiling SQLite to a .lib was no problem, but when linking it to an
> ..exe I got the following:
> sql
yes, after reflecting on it that may be the easiest and less processor
intensive...
Thanks,
Scott
John Elrick wrote:
Scott Derrick wrote:
I have an application that is inserting a record every second. There
are thousands of periods from a few seconds to hours long where the
data in all t
John Machin wrote:
On 5/09/2007 6:18 AM, John Stanton wrote:
These are regular floating point numbers, and behave accordingly.
Utter nonsense. round(98926650.5, 1) -> 98926650.501 is a BUG.
Precisely, As I said, regular floating point.
98926650.5 is representable EXACTLY in "regular
On 5/09/2007 10:13 AM, John Stanton wrote:
John Machin wrote:
On 5/09/2007 6:18 AM, John Stanton wrote:
These are regular floating point numbers, and behave accordingly.
Utter nonsense. round(98926650.5, 1) -> 98926650.501 is a BUG.
Precisely, As I said, regular floating point.
"re
On Tuesday, September 04, 2007 John Machin wrote:
> On 5/09/2007 6:18 AM, John Stanton wrote:
>> These are regular floating point numbers, and behave accordingly.
> Utter nonsense. round(98926650.5, 1) -> 98926650.501 is a BUG.
I agree with you that there is a bug here somewhere. But it is
- Original Message
> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> To: sqlite-users@sqlite.org
> Sent: Tuesday, September 4, 2007 3:32:38 PM
> Subject: Re: [sqlite] 3.5.0 alpha TryEnterCriticalSection linker error
>
>
> =?ISO-8859-1?Q?Daniel_=D6nnerby?= <[EMAIL PROTECTED]> wrote:
> > H
26 matches
Mail list logo