Re: Error in select
Date: Sat, 10 Nov 2012 15:37:39 +1100
Message-ID: <htSdnUIp9-KMRwDNnZ2dnUVZ_oednZ2d_at_westnet.com.au>
Q-IK Q-IK wrote,on my timestamp of 9/11/2012 8:47 PM:
>>
>> Why are you using quotes around the column name?
>>
>> It's not needed, unless you have a very strange way of defining the tables...
>
> When i dont using quotes i have such error:
>
> ORA-00904: "PLANOWANA_DATA": niepoprawny identyfikator
> 00904. 00000 - "%s: invalid identifier"
> *Cause:
> *Action:
> Error at Line: 1 Column: 55
>
Well, like I said: someone used a strange way of creating the table, with mixed upper and lower case characters for column names. NO ONE who has been coding in the database space for a while does even bother doing such. Mostly because it invariably creates a lot of problems down the line. Proof? This very problem you are having.
No, you do NOT need to have column names in mixed case nor is there ANY business or development reason to do such.
So:
1- Stop using that planowano nonsense table in its native form, it was created
by nimcompoops with less brain than a constipated fly.
2- Create a view over that table that includes ALL columns, no predicates and
simply defines all column names in upper case and maps them to the original
nonsense names.
3- Then, simply use the view name and its columns in your php code as if it was
the plano-whatever table.
Received on Sat Nov 10 2012 - 05:37:39 CET