Hello Trevor Talbot,
>> Trevor, I am not sure what you mean by "subselect on its own". Is this what
>> you are looking for?
>
>> sqlite> SELECT * FROM (SELECT * FROM a);
>> SQL error: no such collation sequence: unknown
>
>Yes, exactly. I was curious to see if it made any kind of difference.
>Un
On 11/28/07, Ralf Junker <[EMAIL PROTECTED]> wrote:
> >> Imagine that a SQLite3 database opened in a custom application with a
> >> registered a collation sequence named "unknown" has created the following
> >> table:
> >>
> >> CREATE TABLE a (b COLLATE unknown);
> Trevor, I am not sure what
>> Imagine that a SQLite3 database opened in a custom application with a
>> registered a collation sequence named "unknown" has created the following
>> table:
>>
>> CREATE TABLE a (b COLLATE unknown);
>>
>> Now open this table in the default SQLite3 CLI. Up to here, everything works
>> as ex
On 11/25/07, Ralf Junker <[EMAIL PROTECTED]> wrote:
> Imagine that a SQLite3 database opened in a custom application with a
> registered a collation sequence named "unknown" has created the following
> table:
>
> CREATE TABLE a (b COLLATE unknown);
>
> Now open this table in the default SQLite
Ralf Junker wrote:
Are there any opinions on this list, or should I just post a bug ticket?
Ralf
Imagine that a SQLite3 database opened in a custom application with a registered a
collation sequence named "unknown" has created the following table:
CREATE TABLE a (b COLLATE unknown);
Now
Are there any opinions on this list, or should I just post a bug ticket?
Ralf
>Imagine that a SQLite3 database opened in a custom application with a
>registered a collation sequence named "unknown" has created the following
>table:
>
> CREATE TABLE a (b COLLATE unknown);
>
>Now open this table
6 matches
Mail list logo
