Date: 2004-08-20T07:07:03 Editor: ScottEade <[EMAIL PROTECTED]> Wiki: DB Torque Wiki Page: PostgreSQLFAQ URL: http://wiki.apache.org/db-torque/PostgreSQLFAQ
no comment Change Log: ------------------------------------------------------------------------------ @@ -99,10 +99,12 @@ == What other issues are there? == * Three patch issues in Scarab (quoting various values) [http://nagoya.apache.org/scarab/issues/id/TRQS109 TRQS109][http://nagoya.apache.org/scarab/issues/id/TRQS110 TRQS110][http://nagoya.apache.org/scarab/issues/id/TRQS111 TRQS111] - that these patches need to be applied in order to use PostgreSQL not totally clear (existing test cases all pass). (If someone can confirm that these are required, or better still provide test cases, I will commit them. -- ScottEade 2003-02-05) + * These three patches seek to introduce the use of quoted identifiers in PostgreSQL queries. While this would allow the use of all characters (other than double quotes) in identifiers, it would also make the identifiers case sensitive which may be quite undesirable. -- ScottEade 2004-08-20 * Bill Schneider mentioned on torque-user that "serial" columns are by defaul defined to be of type int4 and that this could pose a problem (the comment may have been made prior to Torque switching from BigDecimal to int for object keys). Note that int4 corresponds to Java int, so this will only be an issue if you need to support a larger range of values than int provides. * Foreign keys to TURBINE_USER. If you have extended your schema to include foreign key references to TURBINE_USER (by way of an alias table definition) the SQL generated to create your database will include foreign key references to the non-existant alias table. This would not have been a problem under MySQL as it ignores foreign ket definitions, however you may need to change your schema in order to be able to use it with PostgreSQL. Torque needs to use the alias table name rather than the alias when generating the sql. * With Turbine 2.3 and the new Torque Security Manager method of extending !TurbineUser this is no longer an immediate problem, but it should still be addressed at some stage. -- ScottEade 2003-10-09 * Multiple unique column definitions are currently generated with the same constraint name. * I have confirmed that this problem is still present in Torque 3.1 and that it applies to index as well as unique. The workaround is to provide the name of the constraint manually using a "name" attribute on the index and unique elements in cases where more than one exists for a given table. -- ScottEade 2003-10-09 + * This has been addressed in 3.1.1 and later. -- ScottEade 2004-08-20 * Columns declared as type CHAR are returned as space padded Strings by PostgreSQL but are not by MySQL. I'm wondering if Troque shouldn't strip the trailing spaces off these automatically. The workaround is to add a setter to the non-Base Torque class for the object that uses String.trim() to remove the spaces. -- ScottEade 2003-11-05 * The jdbc target (torque:jdbc goal in Maven-speak) does not produce the correct DDL SQL for serial columns. -- ScottEade 2004-08-20 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
