if( ap->type==RRCONFLICT ) break;
+ }
+ if( ap==0 ) continue;
+ fprintf(fp,"Degenerated state %d:\n",stp->statenum);
+} else {
+ fprintf(fp,"State %d:\n",stp->statenum);
+}
if( lemp->basisflag ) cfp=stp->bp;
{
(missing ``n'' before ``exprlist'').
Desired effect is achieved (i.e. error, because that statement is not
preparable), however the message is misleading.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlit
ating-point value equal to Y*pow(2,Z).
0 * 2^?? == 0. Zero times positive, finite number gives zero always.
There is no Inf in i64 type to produce NaN from 0 * 2^Inf.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@
ere is a value with the exact
same value inside the database ( executed with the sqlite c++ api without usage
of prepared parameters)
4. Due to 3. if an above query had been working, it would not have
returned any records/rows.
-- best regards
Cezary H. Noweta
__
literally / a person
not existing literally;
A NULL column (blocking) ``action'' in a table ``blocked'' is an error
and should be avoided -- it means ``you are blocked, but I do not know
how''. If someone wants a (lately bound) default action, let the name be
``DEFAU
indices (and
everything what is not strictly designed to enforce an uniqueness)
should be non-UNIQUE ones. IMHO, this fact is worth of recalling in the
doc of UPSERT clause as the fact can become a source of a confusion.
-- best regards
Cezary H. Noweta
_
efer, ...), or
* - defining BIONIC_IOCTL_NO_SIGNEDNESS_OVERLOAD, which will make the
* overloading go away. ''
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
(4)
which adjust referenced xaxis.n and y.axis.n
(4a)
and further DELETE FROM *axis WHERE n == 0
(4b)
and further DELETE FROM *axis WHERE n < nX/nY
(4c)
and further fire UPDATE TRIGGERs of *axis, which in turn further do (4a)
or (4b).
I do not want to provide specified DDL state
Hello,
On 2018-05-04 03:07, R Smith wrote:
On 2018/05/04 1:54 AM, Cezary H. Noweta wrote:
At the beginning I would like to agree with that the problem is
iterative rather then recursive one. However
LOL, that might be the hackiest query I ever seen, but kudos mate,
that's b
x
) SELECT points FROM state WHERE nxmin >= (SELECT nx FROM
params) AND nymin >= (SELECT ny FROM params)
)
UNION ALL
SELECT
SUBSTR(rest, 1, IFNULL(NULLIF(INSTR(rest, ','), 0) - 1,
LENGTH(rest))),
SUBSTR(rest, NULLIF(INSTR(rest, ','), 0) +
justified example of being NULL.) Not every system operates on trillion
records dbs taken from a heaven and executes fancy queries -- there are
also systems which update/insert something and run many relatively
simple queries on a relatively small data.
-- best regards
Cezary H. Noweta
Hello,
On 2018-02-27 08:46, Simon Slavin wrote:
What should substr('abcd',0,-2) return? 'cd' or just 'd'? Or maybe just an
empty string?
NULL
Why?
-- best regards
Cezary H. Noweta
___
sqlite-u
e data even for nonsense input" as design goals,
mapping substr(x,0,z) to substr(x,1,z-1) seems quite a benign solution.
... and as such, that design could be documented.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mai
lated to it) and on your code's side. Additionally, the behavior is
consistent and predictable -- it gives advantages only.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqli
#x27;' identifiers, so you
cannot use them as function names: id ``('' [``DISTINCT''|``ALL''] expr
[, expr [...]] ``)''.
If you want to achieve a desired effect (i.e. ``no such function''
message), then copy block ``expr(A) ::= id(X) LP dist
intf/. Adding ``l''
length modifier makes width/precision specifications being treated as
numbers of UTF-8 chars -- not bytes. ``SELECT length(printf ('%4ls',
'äöü'));'' will give 4.
-- best regards
Cezary H. Noweta
___
Hello,
On 2018-02-19 13:08, Joe Mistachkin wrote:
Cezary H. Noweta wrote:
Use ``Flags=GetAllAsText'' when creating a SQLiteConnection.
Excellent suggestion. Alternatively, you could use the GetString
method on the SQLiteDataReader class.
Indeed, however OP posted that ``GetStrin
his internal cast and just get this information as a text
string, no matter its inside format ?
Use ``Flags=GetAllAsText'' when creating a SQLiteConnection.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglis
memory buffers. In such
case, the C standard handles the situation (look at the end of ``s''
conversion specifier together with ``l'' flag): ``In no case is a
partial multibyte character written.''.
Is there somebody who things about a byte conte
ot;");
... you are using native environment locale (``UTF-8'') for LC_CTYPE?
Behavior entirely unsurprising: there is conversion from L"äöü" using
"UTF-8" LC_CTYPE.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
uld be obviously considered.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
of p->pLimit */
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
text()'' will returns the same memory area
regardless of subsequent numbers of bytes passed. I.e.
sqlite3_aggregate_context(ctx, 1) will return 1byte size memory --
subsequent call (while in the same group of GROUP BY)
sqlite3_aggregate_context(c
solved by someone other (me for sure) then the team.
On the other side, the problem with saturation is completely resolvable
by adding 5 characters to ``Atoi64()''.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqli
, please give me a few hours to cut my
new not-so-completely implemented functionalities from my draft version.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin
re you bringing that argument up. Some kind of argument by an authority?
As you said, probably the problem is an edge one. Probably most people
contending with the problem have found more or less trivial solution. I
have just shared my observations of a bit strange behavior and proposed
till next dusk all the time.
There was no noticeable side effects (besides a performance) in old
32bit INT days, however now, 10 bits of each INT can be going to a vacuum.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
&& c<='9'; i+=incr){
u = u*10 + c - '0';
}
- if( u>LARGEST_INT64 ){
+ if( 19 < i || u>LARGEST_INT64 ){
*pNum = neg ? SMALLEST_INT64 : LARGEST_INT64;
}else if( neg ){
*pNum = -(i64)u;
==
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
e databases, so this breaks it
completely, and I currently had to pin sqlite to an older version which
isn't desired.
IMHO, a better and more concise way is to rem out the following line:
p->mode = p->cMode = MODE_Insert;
in ``shell.c'' and
digits is also enough for the densest range
(<2^-486;2^-485>n<10^-146;10^-145>):
1.FF999x2^-486 => 1.0002594838824945E-146,
1.FF99Ax2^-486 => 1.0002594838824946E-146,
1.FF99Bx2^-486 => 1.0002594838824947E-146.
-- best regards
Cezary H. Noweta
__
patch is trivial also. At least for me, thus, by implication, for the
team. I think that the reason for not extending the pragma lies elsewhere.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
ds (X & ID). The pk has only 1 field (ID)
so why not use that, particularly in the case where ‘ORDER BY ID’ was included in
the query?
OK - your creation statement causes that ``ID'' is an alias for
``rowid''. Why PK is not used, was mentioned by me:
On 2018-0
d? AFAIR you are using SQLite 3.21,
are not you?
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
NG INDEX ...'' means that your index is
used. Order by does not apply as it is the same as PK. Scanning by using
PK results in ORDERed BY PK records. There is no need to use separate
INDEX for ORDER BY clause.
-- best regards
Cezary H. Noweta
__
0
9 Goto 0 1 000
Run Time: real 0.000 user 0.00 sys 0.00
??? My 3.21 checks if NULL is NULL and exits:
2 Null 0 1
3 IsNull 1 9
...
9 Halt 0 0
-- best regards
Cezary H. Now
tain NULLs. :-)
I’m sure I’ve read something before about this but can’t find it in the
documentation?
STH IS STH allows NULLs and returns 1 if both are NULLs, 0 otherwise.
http://sqlite.org/lang_expr.html#isisnot
-- best regards
Cezary H. Noweta
(at
9223372036854775808 -- still much time :-).
``We are programmers and responsible for programming. -O99 is
responsible for thinking. Who in the hell implemented -O when there had
not been -O?'' :-)
-- best regards
Cezary H. Noweta
_
ts in two, long running joins, one of which
goes to a vacuum. I can see real, however negative, computational
advantage. Although that way is a very good academic illustration of
OUTER joins.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing li
Hello,
On 2018-01-03 01:44, Cezary H. Noweta wrote:
MySQL has a separator specified by a distinct clause.
I'm sorry -- I meant ``distinct'' == ``separate/different'' (a clause
named ``SEPARATOR''). Not to be confused with ``DISTINCT''
2879787174<=7821300466>-9054357747<=3166199899>-4120363042<=8151009951>-7018229290<=4454709919<=8212308797
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
7;),('shmorld', '
AND ');
sqlite> SELECT group_concat(a,sep) FROM a GROUP BY NULL;
Hello;world AND shmorld
Hopefully, SELECT FROM SELECT DISTINCT mentioned previously by Scott,
resolves the problem in an easy & painless way.
-- best regards
Cezary H.
Hello,
On 2017-12-29 02:25, Richard Hipp wrote:
Please test the latest trunk version (or any version after check-in
https://www.sqlite.org/src/timeline?c=fd2e0e7a) and confirm that the
modifications work for you.
It works as expected. Thank you.
-- best regards
Cezary H. Noweta
t;
if( esign<0 ){
result = s / scale;
}else{
==
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
...
DateTime: 2017-12-16 15:48:40
DateTime.Kind: Utc
DateTime: 2017-12-16 15:48:40
DateTime.Kind: Utc
==
It looks that your app behaves as if it had default settings:
ISO8601/Unspecified, which results in Local/Unspecified. The sole thing
I have in min
storing/retrieving a valid UTC DateTime, which is stored as
INTEGER. Could you provide your connection string?
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
will fail.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Hello,
On 2017-12-11 01:04, Igor Korot wrote:
On Sun, Dec 10, 2017 at 5:01 PM, Cezary H. Noweta wrote:
On 2017-12-10 07:21, Igor Korot wrote:
The CREATE TABLE statement supports the following syntax:
CREATE TABLE( , CONSTRAINT FOREIGN
KEY() REFERENCES (ref_column_list>);
[...]
nfo about ``FOREIGN KEY''
constraint's name.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
stop time-consuming I/O without
wasting a time for retrieving/writing a data which would be finally
discarded due to an interrupt.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqli
kept,
though it is consistent with the doc (IMHO the doc/specification should
be changed).
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
the
difference between UCS-2 and UTF-16?.)
:-)
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
8 BOMs -- it does not
matter. However, in case of SQLite, Clemens' arguments are very
stringent -- I hope SQLite shell's behavior will not change. For the
sake of the standard conformance, thus predictability and determinedness.
-- best regards
Cezary H. Noweta
___
this.
Certainly, there are no objections to extend an import's functionality
in such a way that it ignores the initial 0xFEFF. However, an import
should allow ZWNBSP as the first character, in its basic form, to be
conforming to the standard.
-- best regards
Cezary H. Noweta
__
is mute about what to except from sqlite3_db_filename().
I agree, that a minor DOC improvement would be nice in this case.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
tunately, ``gcc-7-branch'' still is decompressing on my hardware,
so I cannot check which one(s) of above (a), (b), (c) will help.
Regardless of all, the original problem concerns GCC rather then SQLite
itself.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ch
into the place just after a declaration in the middle of a block, (c) an
using of a pointer to ``res'', and (d) a huge size of ``switch(...)''.
- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
nd
performance increase.
AFAIK, your intention was to remove unnecessary OP_Close (in case of
virtual table cursors). The dangling, problematic OP_Close is at the
very end of ``update.c'' (updateVirtualTable(...)):
sqlite3VdbeAddOp2(v, OP_Close, ephemTab, 0);
-- best
s
treated separately so it could be easy adjusted for consistency.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Close
should be omitted as in SELECT/DELETE?
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Hello,
On 2017-03-29 13:07, Hick Gunter wrote:
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Cezary H. Noweta
Gesendet: Mittwoch, 29. März 2017 12:37
An: SQLite mailing list
Betreff: Re: [sqlite] VT table behavior
from 3.8.5 until now. It is not the best to
rely on the assumption that xOpen-ed cursor is read-only, or have I
missed something? Why xOpen-ed cursor cannot be used to write to a table?
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sq
mand line\n");
rc = 1;
} else {
rc = process_input(&data, in);
fclose(in);
}
free(azCmd);
==
A bit dirty, but works fine though not extremely tested. A cleaner
solution probably requires a bit more work, but due to a shell's thrift
it is quite eas
ing */
} else {
result = sqlite3_exec(db,
"SELECT AVG(salary) AS 'Average salary' FROM employees;",
moneyDisp,
NULL,
&errMsg);
if ( SQLITE_OK != result ) {
/* select error handling */
}
sqlite3_free(errMsg);
re
re.
IMHO, the problem requires redesigning of FTSes or SQLite core (for
example by allowing to disable lastRowid's updating temporarily). I'm
not as fluent in SQLite as to see an ``append-one-line'' solution.
-- best regards
Cezary H. Noweta
__
mands in BEGIN/COMMIT. Until you exec COMMIT,
f5_data is not updated and last_insert_rowid() returns a value set by
``VUpdate'' opcode -- not overwritten by xSync/xCommit updates.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing li
r side, an encryption does not ensure an user separation --
the encryption concerns a whole db-file, so one user having access to an
encrypted db-file could virtually read other user's data.
-- best regards
Cezary H. Noweta
___
sql
Hello,
On 2017-02-21 07:32, Green Fields wrote:
cl sqlite3.c -link -dll -out:sqlite3.dll
cl sqlite3.c -DSQLITE_API=__declspec(dllexport) -link -dll -out:sqlite3.dll
nmake /f makefile.msc
nmake /f makefile.msc DYNAMIC_SHELL=1
-- best regards
Cezary H. Noweta
'' tcl
script option, ``USE_STDCALL'' nmake macro). You can build the
amalgamation in such a way that those macros will appear.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
u
nothing more then a lot of new problems including a nuclear launch :-).
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
t compilers and configurations, but without a success. :-(
``-mrtd'' is not working as good as MSVS' ``-Gz''.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sq
xceeded 2 weeks, but often it fit in minutes, in case of
``normal'' (i.e. not like ``kaksj8ooY^*&^O&rerp66oeri75*&*%P'')
passwords. Good luck.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@ma
provide a decomposition mapping
for ``ł'', or ``Ł''. Even if it is a bug, then it will concern the
Unicode standard rather then SQLite FTS3 itself, as the latter is using
the character database provided by the Unicode standard.
-- best regar
Hello,
On 2017-02-15 01:56, Bart Smissaert wrote:
Downloaded again and now it looks more healthy:
[...]
b0245450e4f27eeefc0da4a871833eb1 sqlite3.c
Still not an original one! MD5 of an original ``sqlite3.c'' is
1efd683943e0d2bce1495b3413e2e235.
-- best regards
Cezary
Hello,
On 2017-02-15 01:26, Bart Smissaert wrote:
OK, that gives this:
[...]
bd6dfd8b2b566ca64ff9f4c637e533f6
That means, you are not using an original, unmodified sqlite3.c file.
Download/unpack an original autoconf package and try once again.
-- best regards
Cezary H. Noweta
-verifier-utility
then run from VS command prompt:
fciv sqlite3.c && nmake /f Makefile.msc
then send the output? You have run a similar command in a response to DRH.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqli
;').
All lines but the last one (containing final ``}'') of the macro must be
ended with ``\'' and a newline. Make sure that newline immediately
follows a backslash, because \ is not recognized as a
line continuation. A splicing physica
N || pColExpr->op==TK_AGG_COLUMN) &&
ALWAYS(pColExpr->pTab!=0) ){
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
plets and
comparison operators in the final WHERE clause because one operation
cancels an effect of other.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
still SQLITE_OK (regardless of what the called function
returned: 0/0.0/NULL or not) then an error has not occurred.
-- best regards
Cezary H. Noweta
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/
Hello,
Would you be so kind as to use ``Write e-mail'' instead of ``Reply''
when you are beginning a new thread?
Thank you in advance.
-- best regards
Cezary H. Noweta
ll xClose releases some resources we would need to know when they
> fail.
You should consider redesigning of your VFS driver architecture in such
a way that releasing is always successful.
-- best regards
Cezary H. Noweta
ll buffering and immediately pass all data down after ``PRAGMA
synchronous = OFF'' (http://sqlite.org/pragma.html#pragma_synchronous).
That is a designed behavior of a VFS driver. If you didn't comply with
that schema, you would play on your own with SQLite's sources.
-- best regards
Cezary H. Noweta
s
rather serious bug which makes a database file corrupted in such a way
that it cannot be repaired. (It can be repaired by copying all data to a
new database or by binary editing of the database file.)
-- best regards
Cezary H. Noweta
s even farther then 3.11.x because it keeps column's declared type
when view's column name has changed (CREATE VIEW v(newname) ...). Thank you.
-- best regards
Cezary H. Noweta
column's id and name are displayed.
> Alternately, you can exploit the explicit column list that is optional
> in a CREATE VIEW:
>
>CREATE VIEW v3 (foo NUMERIC) AS SELECT w+x+y+z AS foo FROM t2;
Syntax error. Did you mean:
CREATE VIEW v3 (foo) AS SELECT CAST(w+x+y+z AS NUMERIC) FROM t2;
-- best regards
Cezary H. Noweta
It seems to me that the most consistent answer is that the "type" of
> columns in a VIEW should always be an empty string.
If so, Mike's postulate is arguable. This fact could be mentioned in a
description of ``table_info'' PRAGMA: in case of views only id and a
name of a column is meaningful.
-- best regards
Cezary H. Noweta
h is not carried in 3.11.x too) is not meaningful
in case of read-only views, then ``affinity'' info is still important
(for comparision).
> Otherwise if this is an unexpected regression then I hope a ticket can
> be filed.
+1.
-- best regards
Cezary H. Noweta
`SELECT'' would return an
empty set, while it returns ``2'' (as in SQLite 3.11.x).
IMHO, this described by you behavior can be considered as a bug in
``PRAGMA table_info'', which takes column's affinity from ``CREATE
TABLE'' command only as for now.
-- best regards
Cezary H. Noweta
Hello,
On 2016-03-29 20:36, Cezary H. Noweta wrote:
> I'm sorry, if I've missed something, but what about Parse::isMultiWrite?
> AFAIK, Parse::mayAbort is used solely in conjunction with
> Parse::isMultiWrite. How can lone Parse::mayAbort influence on
> OP_Transaction (or
e scent, while looking at the SQLite's repository.
-- best regards
Cezary H. Noweta
This allows assertions to be passed, because ``CREATE VIRTUAL TABLE''
does not produce any of ``abortable'' opcodes.
-- best regards
Cezary H. Noweta
to something like:
==
for(z2=&z[1]; sqlite3Fts5IsBareword(*z2); z2++) {
if ( isLastCharOfWord(z2) ) {
z2 = &z2[numberOfBytesOfChar(z2)];
break;
}
}
pToken->n = (z2 - z);
==
However you must notice, that such correction breaks rules mentioned by
Dan Kennedy and have an impact on a whole FTS5 mechanism.
-- best regards
Cezary H. Noweta
Hello,
On 2016-03-22 00:35, James K. Lowden wrote:
>[...] An example from Clang's discussion is
>
> int i = 10 << 31;
Could you provide a link for that discussion? (Or google's phrase to
retrieve such link?)
-- best regards
Cezary H. Noweta
te.org/lang_keywords.html
-- best regards
Cezary H. Noweta
x27;'
to NUMBER?
BWT. The implementation is not broken --- nobody uses broken things. :)
-- best regards
Cezary H. Noweta
followed by digits, or */
'9' >= zNum[i + 1]
) || (
'e' == c || 'E' == c /* has 'e' or 'E'... */
) && (
&zNum[i + 1] < zEnd && (
'0' <= zNum[i + 1] && /* followed by digits... */
'9' >= zNum[i + 1] || (
'-' == zNum[i + 1] || /* or followed by a sign... */
'+' == zNum[i + 1]
) &&
&zNum[i + 2] < zEnd &&
'0' <= zNum[i + 2] && /* and digits */
'9' >= zNum[i + 2]
)
)
);
return hasRealSyntax ? 1 : 3;
}
==
-- best regards
Cezary H. Noweta
INTEGERs!) you must found its offset in
``pData->z'' and extract data from this offset.
If you want to take a control over particular data inserted into a table
then the best method is to use triggers.
-- best regards
Cezary H. Noweta
rpreted as an integer
number is extracted'' and ignoring digits which cause overflow --- the
worst case scenario, as it could introduce many new inconsistencies.
-- best regards
Cezary H. Noweta
Hello,
On 2016-03-14 13:25, Clemens Ladisch wrote:
> Cezary H. Noweta wrote:
>> Is your opinion
>
> Why would my opinion matter, as opposed to what SQLite actually does?
Because, SQLite behaves in a bit strange manner, which is opposite to
extreme carefulness of SQLite in o
1 - 100 of 106 matches
Mail list logo
