in the sql statement, the : if (DB.isOracle()) { sql.append(" ESCAPE '\' "); } fails here I removed it and it went ok
the creation of the unique index sometimes fails ; when trying to add one with a name too long. One of the sql generated : CREATE UNIQUE INDEX TGI_EdiQualitePartie_Trl_UU_uu_idx ON TGI_EDIQUALITEPARTIE_TRL(TGI_EdiQualitePartie_Trl_UU)
Thus we must use only the DB.IsOracle part of the patch ?
Carlos Ruiz
March 5, 2015 at 12:26 AM
Yes @Nicolas Micoud, my point is that we must not have different name of objects in oracle and postgresql - so the name generated must be standard for both dbs if possible.
Nicolas Micoud
February 26, 2015 at 6:51 PM
@Carlos Ruiz I'm using same patch (patch_868_MColumn.patch) in my dev and prod instances (at least for the DB.IsOracle part) and it's ok.
Thanks,
Nicolas
Carlos Ruiz
February 26, 2015 at 4:02 PM
@Nicolas Micoud, I think the name of objects must be consistent in oracle and postgres - so maybe this patch (if still needed) must generate the same name independing of the database
2 kind of errors :
in the sql statement, the :
if (DB.isOracle()) { sql.append(" ESCAPE '\' "); } fails here
I removed it and it went ok
the creation of the unique index sometimes fails ; when trying to add one with a name too long.
One of the sql generated : CREATE UNIQUE INDEX TGI_EdiQualitePartie_Trl_UU_uu_idx ON TGI_EDIQUALITEPARTIE_TRL(TGI_EdiQualitePartie_Trl_UU)
Regards,
Nicolas