On Tuesday 12 February 2008 03:25, Bryce Nesbitt wrote:
> Yes, the view approach has some advantages. But it still leaves the
> underlying tables naked to modification. And since the most likely
> error is... well... me (or another admin) at the SQL prompt, we want
> underlying tables protected
On Tuesday 12 February 2008 03:25, Bryce Nesbitt wrote:
> Yes, the view approach has some advantages. But it still leaves the
> underlying tables naked to modification.
> And since the most likely error is... well... me (or another admin) at
> the SQL prompt, we want underlying tables protected al
Sorry, I think it was misunderstood. I meant that I used the keyword “Order”
as a table property, not as part as the statement
In MS SQL I use [Order] and then just query :
Select [Table1].[Order] from [Table1]
Or
Select [Table1].[order] from [Table1]
In Postgresql I can’t do
I think the grammer should help the parser to determine what you mean when
the token ORDER is seen.
for example in a select statement...
Syntax:
SELECT expression [, ...]
...
[ FROM from_item [, ...] ]
[ WHERE condition ]
...
[ ORDER BY expression [ ASC | DESC | USING operator
Hi, I'm working on migrating a data layer from MS SQL Server to PostgreSQL
8.2 and found that some reserved words should only be written between quotes
and thus are case sensitive (actually only happened with a table field named
"order"). Is there any way to bypass this case sensitivity or at leas
