Due to case weirdness in Postgres, particularly when accessing it from
PHP, I completely abandoned mixed case table and column names. I don't
know if things have changed in the past several years, but when I first
made the leap, mixed case was more trouble than it was worth.
Even after I got over the initial hump and figured out how to make it
work, there was enough weird behavior (i.e. being able to access a
non-existent array element) in PHP that it led to a lot of bugs when
using mixed-case in Postgres. That's my two cents. Your mileage may
vary...
dfx wrote:
> Dear Sirs,
> <snip>
> please note the change of the case of "A" to "a";
>
> if I rename the table to "accoglienza" the error disappear, but arise
> another error on "IdAccoglienza" that change in "idaccoglienza". (i.e.
> all converted to lower case)
>