On Mon, Jan 19, 2015 at 2:01 AM, Stefan Keller sfkel...@gmail.com wrote:
Adding JSON to SQLite (like in PostgreSQL) ultimately needs a
JavaScript parser - and that seems to be against the goal of SQLite
being slim.
It needs a JSON parser, not a JavaScript parser. That's much smaller.
Plus
On my whish-list for this list is the possibility to include attachments like
screenshots and databases.
For program more handy functions and documentation more examples. I'm pretty
sure that less lazy users made functions that could be included as standard to
be used for all of us.
Kind
On 20 Jan 2015, at 12:23am, Klaas V klaasva...@yahoo.com wrote:
On my whish-list for this list is the possibility to include attachments like
screenshots and databases.
I've been active on several technical helplists over the years and from my
experience I'll tell you what would happen.
Hi,
Adding JSON to SQLite (like in PostgreSQL) ultimately needs a
JavaScript parser - and that seems to be against the goal of SQLite
being slim.
But what about adding a data type hash table, i.e. set of keyvalue
pairs (also known as hstore, dictionary or associative array)?
Would'nt this still
Got it, so this should work fine, so long as I'm careful to always re-add
the collate functions to each database handle before accessing the table
with that index. Cool, thanks!
-david
On Sun, Jan 18, 2015 at 1:16 PM, Simon Slavin slav...@bigfraud.org wrote:
On 18 Jan 2015, at 8:29pm, David
Incidentally, I just added this last night to a project I'm working on --
my first custom function! Once again I'm impressed with the power of
sqlite as I went from concept to working implementation in just 2 hours.
I'm using a JavaScript-style query syntax, where you just directly
dereference
On 18 Jan 2015, at 8:29pm, David Barrett dbarr...@expensify.com wrote:
SELECT createNewJSONCollationFunction( FooCollationSequence, foo );
SELECT createNewJSONCollationFunction( BarCollationSequence, bar );
Those two might be okay depending on what the quoted values are meant to be.
We’ll probably look at providing a set of functions for handling JSON in
SQLite, similarly to what POSTGRESQL is doing. But, to make it efficient, we
need to index the JSON content. I suggested earlier this year to get expression
based indexes, so one can index the result of a function like
My wish for the team is to enjoy the holidays, and may the Peace reign in
your homes forever. Thanks for this wonderful tool and may this new 2015
year be one very prosperous! As we say in the Spanish community: Feliz
Navidad y un prospero año nuevo! Gracias.
josé
The only thing on my SQLite wish list is for the development team to
have a meaningful holiday season and a happy, healthy, and productive
new year. The details of the productive part I leave in their capable
hands.
What has been added each year has far surpassed my expectations, and I
have
Native UNICODE?
Dates? UUID (stored as bytes, displayed as string)? I know...new data type
representations are unlikely.
Triggers with declared variables that are preserved across invocations?
(...using temp tables is a pita for storing, say, 5 numbers)
On Sun, Dec 21, 2014 at 4:47 AM, big stone stonebi...@gmail.com wrote:
Hi all,
To prepare for end of 2014 greetings moment, here is my whish list for
2015:
- a minimal subset of analytic functions [1], that I hope may help
end-user/students popularity [2]
- better information on what is
Warner
Sent: Tuesday, December 23, 2014 2:26 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Whish List for 2015
Native UNICODE?
Dates? UUID (stored as bytes, displayed as string)? I know...new data type
representations are unlikely.
Triggers with declared variables
Tony Papadimitriou Sent on Tuesday, December 23, 2014 10:26 AM
Problem 1: Currently, any scripts have to be stored outside the database
in separate files meaning there one-file-holds-everything deal is lost
(and organizing these according to the database they refer also becomes
a bit of an
- 2
Sent: Tuesday, December 23, 2014 5:35 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Whish List for 2015
Tony Papadimitriou Sent on Tuesday, December 23, 2014 10:26 AM
Problem 1: Currently, any scripts have to be stored outside the database
in separate files meaning
Tony Papadimitriou wrote on Tuesday, December 23, 2014 10:48 AM
Can you explain a bit more?
* Who is 'we'? Is this an open source project somewhere?
* How is the combined Lua SQLite3 executable created? Do you have
some makefile (for Windows and Linux) or some instructions for manual
On 23 Dec 2014, at 3:26pm, Tony Papadimitriou to...@acm.org wrote:
CREATE PROC sample AS (
SELECT table1.* FROM table1,...,tableN
WHERE ... possibly complicated join ...
AND last_name like :1
ORDER BY :2;
);
@sample 'Smith%',tax_id
would become:
SELECT table1.* FROM
On Tue, Dec 23, 2014 at 05:26:00PM +0200, Tony Papadimitriou wrote:
Proposal:
Minimal stored procedure functionality -- or, maybe call it stored
It's already there. It's called TRIGGER.
I use triggers to hold stored procedures, and WHERE conditions on DMLs
in the trigger body as
Hi SQLite team:
I cast my vote for some analytic functions too.
-Original Message-
From: big stone stonebi...@gmail.com
To: sqlite-users sqlite-users@sqlite.org
Sent: Sun, Dec 21, 2014 1:47 am
Subject: [sqlite] Whish List for 2015
Hi all,
To prepare for end of 2014 greetings moment
Hi all,
To prepare for end of 2014 greetings moment, here is my whish list for
2015:
- a minimal subset of analytic functions [1], that I hope may help
end-user/students popularity [2]
- better information on what is coming ahead, for example:
. I see the 'sessions' tree moving along main
For your second point, SQLite4 may never be released, or if it is going
to be, not for a few years yet. 4 is a toy for the devs to try things out
without borking things up in 3. 3 is being used by millions (or is it
billions?) of devices and applications that the dev team is (very right) in
not
On Dec 21, 2014, at 10:47 AM, big stone stonebi...@gmail.com wrote:
- a minimal subset of analytic functions
+ MERGE! Yeah!
Happy Holidays!
___
sqlite-users mailing list
sqlite-users@sqlite.org
On 21 Dec 2014, at 2:39pm, Stephen Chrzanowski pontia...@gmail.com wrote:
SQLite4 may never be released, or if it is going
to be, not for a few years yet.
SQLite 4 can be whatever gets released next. It may be nothing like SQLite4 is
now. Next month one of the developer team may have
On Sun, Dec 21, 2014 at 11:28 PM, Simon Slavin slav...@bigfraud.org wrote:
When you're wishing for the future, however, it's best to wish big, not
for a tiny step-wise improvement. Don't wish for a system with a better
journalling mode, wish for a system without 17 journalling different
On 21/12/14 09:47, big stone wrote:
that I hope may help end-user/students popularity [2]
[2] http://db-engines.com/en/ranking_trend
The methodology used by that site is tilted in favour of big data, and
complex databases. Consequently, even if there are ten million SQLite
databases for
On 21 Dec 2014, at 10:01pm, jonathon toki.kant...@gmail.com wrote:
On 21/12/14 09:47, big stone wrote:
that I hope may help end-user/students popularity [2]
[2] http://db-engines.com/en/ranking_trend
The methodology used by that site is tilted in favour of big data, and
complex
26 matches
Mail list logo
