Most interestingly, a case of duplicate column names check that seems to
have slipped through the net allowing a table to have three columns
named the same, but only if they're empty and the user has used a
different delimiter set each time (which by the way is discouraged and
we should stick to
I read that VALUES(expr-list) means the same as SELECT(expr-list), but
apparently not with regards to the metadata that's sent out along with
the values.
If I issue these two commands, in one case I end up with column names
"", ":1", ":2" (sequential), and in the other I end up with "1", "2",
On 2015-06-17 9:50 PM, david at andl.org wrote:
> The question for now is: does a new database programming language have a
> place?
When you ask the question as broadly as that, the answer is most definitely
"yes".
Just look at the wider world and you see there are dozens of application
The aftermath...
dir *. /x /b
h8 08 @_8 0o8 hN Q N xa8 b8 0f8
10 soubor?, 14,336 bajt?
I took that the .open command could be issued as ".open" to open a new
in-memory database and ".open ''" (followed by a pair of single quotes)
to open a new unnamed temporary file database.
I wonder what is going on here: After issuing a short combination of
these commands with/without putting
I have created a table to store images. The columns are file name and file
content. FileContent field is the blob.
I am using Samsung Tablet with Android Version 4.4.2. Most of the tablets that
I tested the software in, it works fine.
However, on one specific Android table I am having
The override of match() trick works pretty well for cases like this. I've
overridden match in my virtual table implementation to allow me to pass
arbitrary specialized queries directly to my virtual table modules for cases
that I know the virtual table can do a better job that SQLite on that
I agree.
SQL is quite deficient in terms of set-oriented updates. INSERT is more or
less UNION, but UPDATE and DELETE have no set-oriented forms.
The relational algebra describes operations on sets of tuples, where the
only operation on attributes is to compare them by name or equal value. SQL
A recursive function contains a computation and a decision: whether to
terminate or go deeper. Any recursive function/query will fail to terminate
if the termination condition is not satisfied.
Here are two similar CTEs. The first terminates, the second does not.
WITH RECURSIVE
cnt(x) AS
Thank you for the comments.
Andl already has regular expressions and compound datatypes. They do
everything you list here. [Regex is pretty obvious, and user types are as
per TTM.]
Namespaces: interesting idea. I'm not sure a hierarchical model is the best
choice, but I can definitely see that
Thank you for your comments.
My target is developers, particularly those who are strong on the business
domain knowledge and UI/UX, but not so strong on the database stuff. My aim
is that they can write code to do sophisticated queries and data
manipulation without becoming an SQL guru and
> -Original Message-
> From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-
> users-bounces at mailinglists.sqlite.org] On Behalf Of david at andl.org
> Sent: Monday, June 15, 2015 2:28 AM
> To: 'General Discussion of SQLite Database'
> Subject: Re: [sqlite] Mozilla wiki
Should be fixed now on trunk.
On 6/17/15, Jean Chevalier wrote:
> I took that the .open command could be issued as ".open" to open a new
> in-memory database and ".open ''" (followed by a pair of single quotes)
> to open a new unnamed temporary file database.
>
> I wonder what is going on here:
Jerry wrote:
> With xBestIndex and xFilter, we can pass the constraint information (e.g.,
> those from WHERE clause) to virtual table (through struct
> sqlite3_index_info), so that we can locate the cursor to narrow the search
> space.
> However, it does not provide information about functions
On 17 Jun 2015, at 3:44am, Marc L. Allen wrote:
> I don't know. Back in the day, assembly was low-level because it was directly
> converted to machine code. C was high level because you could express more
> complex structures without worrying about the underlying architecture.
C was
Marco,
>There's never been that kind of tone, the article has been written to
>point
>new Mozilla codebase contributors at possible pitfalls we already hit in
>the past, and actually help them making informed decisions.
That's not how one reads it. Start with only the title:
16 matches
Mail list logo
