Yuri Timofeev wrote:
> Hi
> 
> 
> Reynier Pérez Mira wrote:
> 
>     What you mean with "Bacula some incomprehensible confusion with the
>>     naming of tables and fields in various registers in the DBMS MySQL and
>>     PostgreSQL"? I don't understand the problem.
>>
> 
> 
> I explain. See:
> 
> src/cats/make_mysql_tables.in
>   CREATE TABLE Filename
> 
> 
> src/cats/make_postgresql_tables.in
>   CREATE TABLE filename
> 
> That's why I can not write code that would work with mysql and postgresql.
> filename != Filename
> 
> Example:
> 
> this code
>   $select->from('Filename', ...
> will work with mysql
> and receive an error message php PDO, if the DBMS will be postgresql.
> 

Ok this seem to be a bug ... and certainly should be reported to bugs.bacula.org
And would be nice to have it for 2.4.1


Having a consistent db sql all around db engine is a minimum.
We can imagine what type of trouble a customer could encounter if they move 
from mysql to postgresql or vice versa.

After that mysql by default on myisam table doesn't care about sensitive case.

Let me a message on the mailing liste if you need my help to help about that.

-- 

     Bruno Friedmann

Ioda-Net Sàrl   - www.ioda-net.ch
  2830 Vellerat - Switzerland



-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users