Quoting Toby Thain <[EMAIL PROTECTED]>:
>
> On 13-Oct-08, at 7:15 AM, Markus Hoenicka wrote:
>
>> Hi,
>>
>> just to clarify: it is sqlite, not the sqlite driver which does not
>> support newlines in SQL statements.
>
> Wow, that's inconvenient. I imagine that must break very many ORM/SQL
> generat
On 13-Oct-08, at 7:15 AM, Markus Hoenicka wrote:
> Hi,
>
> just to clarify: it is sqlite, not the sqlite driver which does not
> support newlines in SQL statements.
Wow, that's inconvenient. I imagine that must break very many ORM/SQL
generating layers.
--Toby
> Some other SQL engines like M
Hi,
Never any intention to fix the parsing in the driver ;)
The sql92 standard says nothing about newlines in the sql statments, and
are defined more like complete sentences.
The select statement parsing in the driver parses according to the
select definition at sqlite.org -> http://sqlite.org/lan
Hi,
just to clarify: it is sqlite, not the sqlite driver which does not
support newlines in SQL statements. Some other SQL engines like MySQL
do support newlines, so this appears to be a design decision (I don't
know what the standard says). To verify, use these SQL scripts:
-
select
ve
The parsing of the sql statement will fail at the first new line char as
this indicates the end of the c-string.
This is the first time I have seen newline characters explicitly
embedded in an sql statement. Is there a reason that the newline
characters are needed ?
Brecht Sanders wrote:
> Hi,
>
Hi,
I was just testing a program I'm making that uses libdbi. My test was
with an sqlite database.
I came across the following problem:
When a query contains a newline (\n) instead of space on certain
positions dbi_result_get_field_type_idx always returns DBI_TYPE_STRING.
An example of such query
