Jason Crummack wrote:
> When approaching database related issues I afraid I can't take the
> approach of it works alright for me,
No. Neither can way, but don't be too hard on Alexander; he was a raw noob
when he first got involved with DBIx::Class and has made valuable
contributions in spite o
Alex,
If I could predict what new reserved words may appear in future Oracle /
SQL versions I would, that's the reason they give you a quote character
to allow future changes to reserved words.
I agree that if I was creating new tables, I wouldn't at this point in
time use a currently known re
Hi Jason!
I haven't quoted my tablenames on creation (whatfor?) so all my tables are case
insensitive and I didn't bother with quotes.
Reserved words are reserved for a good reason, I don't see the point of using a
reserved word as table name.
Fell free to send a patch for Storage::DBI::Oracle
