Zsbán Ambrus wrote:
> CREATE TABLE tab(amt DEFAULT (max(1)));
SQLite also accepts parameters:
CREATE TABLE t(x DEFAULT(?));
(Other places like CHECK constraints do check for this, so this appears
to be an oversight.)
Regards,
Clemens
___
sqlite-use
On Tue, Aug 5, 2014 at 4:55 PM, Richard Hipp wrote:
>
>
>
> On Tue, Aug 5, 2014 at 4:15 PM, Zsbán Ambrus wrote:
>
>> Dear sqlite3 maintainers,
>>
>> I've got a segmentation fault when trying to execute the following two
>> statements in the sqlite 3.8.5 command line program:
>>
>> CREATE TABLE t
On 5 Aug 2014, at 9:15pm, Zsbán Ambrus wrote:
> CREATE TABLE tab(amt DEFAULT (max(1))); INSERT INTO tab DEFAULT VALUES;
How on earth did you find that ?
Nice catch, by the way. If Dr. Hipp is correct, that's a bug which has existed
for longer than 8 years, or probably ever since SQLite3 exis
On Tue, Aug 5, 2014 at 4:15 PM, Zsbán Ambrus wrote:
> Dear sqlite3 maintainers,
>
> I've got a segmentation fault when trying to execute the following two
> statements in the sqlite 3.8.5 command line program:
>
> CREATE TABLE tab(amt DEFAULT (max(1))); INSERT INTO tab DEFAULT VALUES;
>
The tick
Dear sqlite3 maintainers,
I've got a segmentation fault when trying to execute the following two
statements in the sqlite 3.8.5 command line program:
CREATE TABLE tab(amt DEFAULT (max(1))); INSERT INTO tab DEFAULT VALUES;
I believe this is a bug, because the vanilla command line should not
segfa
5 matches
Mail list logo
