On 4/4/19 11:35 PM, Simon Slavin wrote:
> On 5 Apr 2019, at 4:14am, Richard Damon wrote:
>
>> I think is logic is to attempt to insert a row, and if rather than
>> inserting it, the call returns the error condition, 'Database Full'
> Okay. So now we understand what OP meant by the database being
On 5 Apr 2019, at 4:14am, Richard Damon wrote:
> I think is logic is to attempt to insert a row, and if rather than
> inserting it, the call returns the error condition, 'Database Full'
Okay. So now we understand what OP meant by the database being full.
SQLITE_FULL does not mean 'Database
I think is logic is to attempt to insert a row, and if rather than
inserting it, the call returns the error condition, 'Database Full', you
remove a record and then try again (a form of error recovery), if it
succeeds, then you go on and get more data.
If full was X records, then they would
On 4 Apr 2019, at 10:12pm, Lifepillar wrote:
> This is essentially a pragmatic choice, as the semantics of NULLs is
> unspecified and ambiguous.
The way SQL handles NULLs may sometimes appear inconsistent, but is the result
of SQL handling rows as sets. Some of the behaviour is, carefully
On 4 Apr 2019, at 21:36, James K. Lowden wrote:
>
> On Thu, 4 Apr 2019 17:30:29 +0200
> Lifepillar wrote:
>
>> On 4 Apr 2019, at 17:15, James K. Lowden
>> wrote:
>>> On Wed, 3 Apr 2019 14:30:52 +0200
>>> Lifepillar wrote:
SQLite3 Decimal is an extension implementing exact decimal
On Thu, 4 Apr 2019 11:21:41 -0400
Joshua Wise wrote:
> > On the other hand, what table has a floating point number in its
> > key?
> >
> > How do you even express the value of such a key for an exact
> > match?
>
> Well I imagine it can be very useful for range queries. Imagine
> Julian
On Thu, 4 Apr 2019 17:30:29 +0200
Lifepillar wrote:
> On 4 Apr 2019, at 17:15, James K. Lowden
> wrote:
> > On Wed, 3 Apr 2019 14:30:52 +0200
> > Lifepillar wrote:
> >> SQLite3 Decimal is an extension implementing exact decimal
> >> arithmetic for SQLite3.
> >
> > What does divide-by-zero
On 4 Apr 2019, at 17:30, Lifepillar wrote:
>
>> You have the option to ignore the error, though, in which case you get +Inf:
>
> sqlite> delete from decTraps where flag = 'Division by zero';
> sqlite> select decStr(decDiv(1,0));
> Infinity
Forgot to mention that in this case a flag is silently
On 4 Apr 2019, at 17:15, James K. Lowden wrote:
>
> On Wed, 3 Apr 2019 14:30:52 +0200
> Lifepillar wrote:
>
>
>> SQLite3 Decimal is an extension implementing exact decimal arithmetic
>> for SQLite3. It is currently unfinished and under development.
> ...
>> I welcome any feedback, from the
Hi!
I don't know if this has been already discussed, most probably yes. But are
there any plans to implement the possibility to add constraints to existing
tables? And I'm not necessarily asking for full-blown functionality. Currently
to do that you have to drop the table and recreate it again
> On the other hand, what table has a floating point number in its key?
>
> How do you even express the value of such a key for an exact match?
Well I imagine it can be very useful for range queries. Imagine Julian dates,
coordinate points, rankings, etc.
I suppose in the most common case,
On Wed, 3 Apr 2019 14:30:52 +0200
Lifepillar wrote:
> SQLite3 Decimal is an extension implementing exact decimal arithmetic
> for SQLite3. It is currently unfinished and under development.
...
> I welcome any feedback, from the super-technical to the
> end-user oriented. There is no manual so
On Wed, 3 Apr 2019 11:37:47 -0600
Warren Young wrote:
> Put another way, your defaults are already so large that no
> conceivable physical entity could build a computer big enough to
> simultaneously contain every distinct state your data type represents.
Exactly (as it were).
Physical
On Wed, 3 Apr 2019 17:29:47 -0400
Richard Hipp wrote:
> On 4/3/19, Joshua Wise wrote:
> > From my naive understanding, memcmp() is used to efficiently
> > compare long strings of bytes. But where in SQLite3 is it necessary
> > to compare long strings of floating point numbers? I, of course,
> >
This almost sounds like "Full" is a software limitation, in that your
application is specifying that "Full" means you can only have "X" number of
rows.
If you're looking to remove data, I'd suggest that you find some way to
isolate the oldest record, either by a row identifier (Like an ID field
Nice one Simon,
as a resident Australian (and a lover of levity) I liked your link, which
led me on to the data source. I took a pair of those 15 digit coordinates
and pumped them into good old Google maps but sadly I was unable to zoom in
far enough to see any chlorine atoms. :-(. Shame that.
On 4 Apr 2019, at 10:37, Thomas Kurz wrote:
>
> I appreciate your effort towards this extension. In my opinion, however, this
> is (along with bigint-support) a feature that belongs into core (for that
> reason alone to get math operations, comparisons, aggregates, etc. working in
> an
Up to now, we were doing 2-tables full-outer-join using the classic
emulation, since SQLite lacks support for that join.
But now we are doing it with 3 tables, and it gets ugly fast IMHO.
https://stackoverflow.com/questions/12759087/full-outer-join-in-sqlite-on-4-tables
I "think" the reason
On 4/4/19 2:07 AM, Arthur Blondel wrote:
> Hello
>
> When I try to insert new data to a full SQLite database, I need to remove
> much more than really needed. I'm doing the following:
>
> while(1) {
> do {
> status = insert_1_row_to_db();
> if (status == full) {
>
This looks to be an example of the classic XY Problem. You are asking
how to solve Problem X when what you're trying to do is solve Problem
Y. In this case, "X" is a full database, which is almost certainly an
oxymoron since SQLIte can store millions of rows of data. It is not
clear what
Thank you all for these tips. Very helpful!
Op di 2 apr. 2019 om 08:35 schreef Rowan Worth :
> On Mon, 1 Apr 2019 at 19:20, Domingo Alvarez Duarte
> wrote:
>
> > Hello Gert !
> >
> > I normally do this (be aware that if there is a power outage the
> > database is screwed):
> >
> > ===
> >
> >
> When the database is full
What do you mean by a full database? Do you mean when the operating system
has run out of disk space?
A SQLite database can hold millions of rows, so technically, a database
cannot be 'full'.
It would be easier explaining the full issue and what you consider the
Hello
When I try to insert new data to a full SQLite database, I need to remove
much more than really needed. I'm doing the following:
while(1) {
do {
status = insert_1_row_to_db();
if (status == full) {
remove_one_row_from_db();
}
} while (status ==
I appreciate your effort towards this extension. In my opinion, however, this
is (along with bigint-support) a feature that belongs into core (for that
reason alone to get math operations, comparisons, aggregates, etc. working in
an intuitive way).
Years ago, for SQLite4, there seem to have
If you're trying to copy a file while connections still have it open
then you should use SQLite API calls to do it. The obvious ones are
in the SQLite Online Backup API, which is the set of calls underlying
the '.backup' command you mentioned. You can find documentation for
this here:
25 matches
Mail list logo
