standalone seems reasonable.
To confuse things further, I have seen Sqlite embedded in an embedded
web server, serverless doesn't fit that case.
On Tue, Jan 28, 2020 at 9:45 AM Jose Isaias Cabrera wrote:
>
>
> Richard Hipp, on Monday, January 27, 2020 05:18 PM, wrote...
> >
> > For many years
> I’ve spent too much time lately trying to figure out or debug hellacious C
> spaghetti code
And I’ve spent too much time lately trying to figure out or debug
hellacious C++ spaghetti code
Someone who writes bad C, will write even worse C++
___
3.30.1 x86_64 Linux
Same problem here.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Number one on my wishlist.
UNSIGNED
Wanted for ordering more than anything else
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
In applications dates/times are input, dates/times are output.
Commonly the storage format of dates/times is of no concern.
More effort is often spent on time zone display and input, which is an
application issue rather than a data store issue. (e.g. fossil)
All one *needs* is database functions
Note https://www.sqlite.org/datatype3.html says:
"Applications can chose to store dates and times in any of these
formats and freely convert between formats using the built-in date and
time functions."
This is partially true. The date and time functions will optionally
parse 'a timezone indicator
Hi Stephen,
I have a SQLite database that was ported from mysql. Most of the
column definitions remain unchanged.
There is lots of CHAR and VARCHAR definitions and contrary to Simon's
response they mean what they say.
90+ % of the data is fixed length CHAR. (codes and fixed labels).
When the
Whilst playing with fossil, I have encountered what I believe to be a
deficiency in strftime() (and friends).
As the Sqlite documentation states, dates supplied to the date
functions may have a timezone suffix i.e. "[+-]HH:MM" or just "Z".
The Sqlite input date parsing is faultless to my testing.
Agree with all that.
> A way to skip a header row when the table exists would be useful.
>
How about
> .header on/off
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
> For good or bad, check constraints appear to be evaluated before this
>
conversion.
I call that very bad.
On Wed, Mar 20, 2019 at 7:58 AM Shawn Wagner
wrote:
> A manual INSERT demonstrates the same behavior, actually. Using your Tc
> table:
>
> sqlite> insert into Tc values ('12');
>
The big downside of the csv extension, is that no matter what you do your
table ends up with every column with a type of text.
A trap if you are you are using union/except/intersect clauses.
On Fri, Mar 8, 2019 at 11:00 AM Keith Medcalf wrote:
>
> On Thursday, 7 March, 2019 14:45, Eric Tsau
Does ROLLBACK release the transaction lock on the database ?
I checked scripts on this. Yes.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
if I understand the question:
On Sun, Mar 3, 2019 at 10:12 AM Simon Slavin wrote:
> Does ROLLBACK release the transaction lock on the database ?
>
I think so or my code would not be working.
>
> Does ROLLBACK cancel the BEGIN ? Or do I need to issue END ?
>
END is a synonym for commit . So
n the two places of the documentation are different.
On Wed, Feb 13, 2019 at 7:01 PM Simon Slavin wrote:
> On 13 Feb 2019, at 6:09am, D Burgess wrote:
>
> > 3.6.20 is a loong time ago. Which led me to think that maybe that list
> is no longer be accurate.
> > Is there an easy
known by the code generators includes:"
3.6.20 is a loong time ago. Which led me to think that maybe that list is
no longer be accurate.
Is there an easy way to extract the available options for the latest
release?
On Wed, Feb 13, 2019 at 5:02 PM Simon Slavin wrote:
> On 13 Feb 2019,
Is there a definitive list of "defines" for building the amalgamation.
i.e. for the following two steps
$ ./configure
$ ./make sqlite3.c
I build the Amalgamation because I need ENABLE_UPDATE_DELETE_LIMIT.
___
sqlite-users mailing list
On Wed, Feb 6, 2019 at 11:26 AM Keith Medcalf wrote:
"you have not normalized the data before storing it"
This is true of most of the hundreds, if not thousands, of schema that I
have seen.
___
sqlite-users mailing list
There is also a problem with the documentation on csv.c
Example from the source comments:
CREATE VIRTUAL TABLE temp.csv2 USING csv(
filename = "../http.log",
schema = "CREATE TABLE x(date,ipaddr,url,referrer,userAgent)"
);
It should be noted that the schema= parameter
> Banks still use, as they have for a very long time, Binary Coded
> Decimal, or some equivalent that does not suffer from a loss of
> accuracy, so all this foofaraw to do with floating point representation
> of various amounts of currency does not apply to the real world.
>
> Cheers,
>
> The CoC is fine. Don't change it.
+1
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
select strftime('%Y-%m-%d %H:%M', '2018-09-23 8:59', 'localtime','weekday
0');
Also gets a bit confusing. The "weekday" operates on the UTC time.
On Sun, Sep 23, 2018 at 11:42 PM, Kevin Martin wrote:
> Hi,
>
> Not sure if this is me misreading it, but the description of the weekday
>
Thank you E.Pasma, most elegant. Solves my problem.
Thank you Rowan, I was trying to achieve it with /bin/sh (dash)
On Tue, Sep 18, 2018 at 7:12 PM, E.Pasma wrote:
>
> > Rowan Worth wrote:
> >
> > You can also filter out specific messages at the shell level:
> >
> > sqlite foo.db 2> >(grep -v
tains anything written
> there
>
> -Ursprüngliche Nachricht-
> Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
> Im Auftrag von D Burgess
> Gesendet: Dienstag, 18. September 2018 08:15
> An: sqlite-users@mailinglists.sqlite.org
> Betreff: [EXTERNAL] [sqlite] shell
I have a script that loads csv into an existing table.
I get this message on stderr for each row imported:
"... expected 7 columns but found 6 - filling the rest with NULL"
We have the means to send stdout to /dev/null using the .once or .output
Is there a way to send suppress stderr messages
The original question was that I was curious about the history.
Noting where we are now at, I will give as examples of two real world
applications:
1. 32 bit embedded sqlite. Realtime storing data from various hardware
interfaces.
The data includes unsigned 32 bit integers which are stored as
To answer Jens - electronic IDs.
And yes I use bignums on the client side.
Note that I have workarounds and the system I have is stable and
works, I just rue not having 64 bits and UNSIGNED indexes.
There was additional work to get it all going in SQLite. I probably
would not have originally
I currently store them as blobs. A lot of them, 16 bytes (versus
numeric 8 per item).
And not optimal for indexes.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> You can just store binary blobs and interpret then in the client, no? Or do
you need to do arithmetic on them?
Not arithmetic, but &, |, <<, >>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
gt; example:
>
> sqlite> INSERT INTO b2 VALUES ("2");
> Error: constraint failed
>
> The TYPEOF check rejects this, but without that constraint:
>
> sqlite> INSERT INTO b VALUES ("2");
> sqlite> SELECT c, TYPEOF(c) FROM b;
> 15|integer
>
Is there a historical reason why sqlite does not have a UNSIGNED type
to go with INTEGER?
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
te-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
--
D Burgess
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On the systems I use, for log files, you cant beat a text file for
integrity and speed.
I would suffer the slower queries and use something like the CSV
extension on your text log files.
On Mon, Jul 30, 2018 at 10:44 AM, Simon Slavin wrote:
> I have a particular logging task which is
32 matches
Mail list logo
