You can eliminate separators by using
.mode list
.sepa ""
But then you need to format your values to the correct widths for the record
description. Text processing is not the primary domain of SQLite and is best
left to the presentation layer.
Alternatively you may consider writing a virtual ta
In the vdbeaux.c source, the function
resolveP2Values(...)
is not resetting p->readOnly when it encounters an OP_VUpdate opcode
is not setting p->bIsReader when it encounters an OP_VFilter opcode
Additionally, the frunction
sqlite3VdbeHalt(...)
is only checking p->bIsReader and omitting to c
Hi *,
while working on a database upgrade on our application I found a bug in
SQLite. I was adding a not null constraint by updating the sqlite_master
table and to see the check fail used pragma integrity_check to find the
offending rows that I know are there.
However, the integrity check just pa
On 13 Oct 2016, at 3:46pm, Torsten Landschoff
wrote:
> while working on a database upgrade on our application I found a bug in
> SQLite. I was adding a not null constraint by updating the sqlite_master
> table and to see the check fail used pragma integrity_check to find the
> offending rows th
Thank you, Gunter. I will investigate virtual tables; it's a bit over my
head at the moment.
My final implementation was to route the select via .output, employ a CTE
to prepare the data, use printf to setup the record format, and then select
the data from the CTE. Again, I do not enjoy the redund
If you're using the CLI exclusively you can go into shell.c and get rid of the
double spaces. In the copy I'm looking at that's bundled with the 3.14.2
amalgamation it looks like there're 5 lines to alter and you'll be good.
They're in
static int shell_callback(
...
case MODE_Column: {
...
Line
On 10/14/2016 04:59 PM, Hick Gunter wrote:
In the vdbeaux.c source, the function
resolveP2Values(...)
is not resetting p->readOnly when it encounters an OP_VUpdate opcode
is not setting p->bIsReader when it encounters an OP_VFilter opcode
Additionally, the frunction
sqlite3VdbeHalt(...)
is
In the Row Values page http://www.sqlite.org/rowvalue.html, section 2.2 there’s
an extra semicolon in the code box, turning it into 2 statements.
UPDATE tab3
SET (a,b,c) = (SELECT x,y,z
FROM tab4
WHERE tab4.w=tab3.d);
WHERE tab3.e BETWEEN 55 AND 66;
While we're on the subject there are at least two grammatical errors on the
same page:
there is no substitutions
and
A NULL means of "unknown"
On Friday, October 14, 2016 12:20 PM, David Raymond
wrote:
In the Row Values page http://www.sqlite.org/rowvalue.html, section 2.2
there’s
Thanks, David. I can read C, but I don't know how to compile it. :( Just
not a language I have learned.
On Fri, Oct 14, 2016 at 10:22 AM, David Raymond
wrote:
> If you're using the CLI exclusively you can go into shell.c and get rid of
> the double spaces. In the copy I'm looking at that's bund
Two more in here:
or an ISO-8601 dates string. But some application store dates
On Friday, October 14, 2016 12:27 PM, Robert Weiss
wrote:
While we're on the subject there are at least two grammatical errors on the
same page:
there is no substitutions
and
A NULL means of "unknown"
On 10/14/16, David Raymond wrote:
> In the Row Values page http://www.sqlite.org/rowvalue.html, section 2.2
> there’s an extra semicolon in the code box, turning it into 2 statements.
>
>
> UPDATE tab3
>SET (a,b,c) = (SELECT x,y,z
> FROM tab4
>WHERE tab4
On Oct 14, 2016, at 1:27 PM, Don V Nielsen wrote:
>
> I can read C, but I don't know how to compile it.
https://www.sqlite.org/howtocompile.html
Once you get SQLite to build, make the suggested change and say “make” again.
The sqlite3 program will be rebuilt, since make knows that sqlite3 dep
Not that I don't enjoy this conversation, but this should be end of this
thread. Thanks for telling me to look at shell.c. I did. Interesting read.
I can see that simply changing " " to "" in the printf call, recompiling,
and tada, I have what I want. Thanks David.
- HOWEVER -
New logic is requ
14 matches
Mail list logo