ode out there relies
> on this feature, so it's difficult to remove.
>
> Igor Tandetnik
>
>
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
KurDtE wrote:
> I'm getting pretty confused :
> When I execute the query SELECT "GENERAL.ID" FROM VIEW_GENERAL; on
> SQLite Administrator (which uses an older version of SQLite than
> 3.6.10), everything works fine, but when I try the same query with
> SQLite 3.6.10 on command
; sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
>
--
View this message in context:
http://www.nabble.com/SELECT-issue-with-SQLite-3.6.10-tp21682817p2168908
2.html
Sent from the SQLite mailing list archive at Nabble.com.
mechanisms for compatibility
> with other database engines. [...] is used by MS SQL Server. `...`
> is used by MySQL.
>
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> ___
> sqlite-users mailing list
> sqlite-users
Subject: Re: [sqlite] SELECT issue with SQLite 3.6.10
On Jan 27, 2009, at 10:08 AM, Fred Williams wrote:
>
> Should not the GENERAL.ID be enclosed in double quotes? Or did I
> misread
> the SQL Standard?
You can use double-quotes to conform to the SQL standard. But SQLite
also all
On Jan 27, 2009, at 10:08 AM, Fred Williams wrote:
>
> Should not the GENERAL.ID be enclosed in double quotes? Or did I
> misread
> the SQL Standard?
You can use double-quotes to conform to the SQL standard. But SQLite
also allows some non-standard quoting mechanisms for compatibility
of SQLite Database
Subject: Re: [sqlite] SELECT issue with SQLite 3.6.10
On Jan 27, 2009, at 5:24 AM, KurDtE wrote:
>
> Dear all,
>
> Yesterday I upgraded my SQLite version from version 3.5.9 to 3.6.10,
> and I
> now experience an issue while making a SELECT on one of my vie
On Jan 27, 2009, at 5:24 AM, KurDtE wrote:
>
> Dear all,
>
> Yesterday I upgraded my SQLite version from version 3.5.9 to 3.6.10,
> and I
> now experience an issue while making a SELECT on one of my view :
>
> This query was previously working on version 3.5.9 :
> SELECT [GENERAL.ID] FROM
f a column in the view.
I now get this error : GENERAL.ID : no such column.
I think it gets confused with the dot, how to make the query understand it
as column name, and not table name + column name ?
Thanks for help,
Regards,
Anthony
--
View this message in context:
http://www.nabble.com/SE
9 matches
Mail list logo