[jira] Commented: (DDLUTILS-103) Upgrade version of commons-betwixt in pom.xml
[ http://issues.apache.org/jira/browse/DDLUTILS-103?page=comments#action_12376957 ] Ken Weiner commented on DDLUTILS-103: - Putting 0.8-SNAPSHOT depends on whether or not DdlUtils is supposed to depend on the most recent code base of commons-betwixt leading up to the 0.8 release or a specific patched version which DdlUtils is calling 0.8-dev. I thought it was the latter in which case the term SNAPSHOT would be misleading. Upgrade version of commons-betwixt in pom.xml - Key: DDLUTILS-103 URL: http://issues.apache.org/jira/browse/DDLUTILS-103 Project: DdlUtils Type: Improvement Components: Core Reporter: Ken Weiner Assignee: Thomas Dudziak The pom.xml for building with Maven has common-betwixt at version 0.7 but it should be changed to 0.8-dev to match the version checked into the lib directory: dependency groupIdcommons-betwixt/groupId artifactIdcommons-betwixt/artifactId version0.8-dev/version /dependency Certain problems arise when using DdlUtils with an older version of commons-betwixt. For example, the unique element of the schema gets mistakenly added as a column. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DDLUTILS-103) Upgrade version of commons-betwixt in pom.xml
[ http://issues.apache.org/jira/browse/DDLUTILS-103?page=comments#action_12376506 ] Ken Weiner commented on DDLUTILS-103: - Can commons-betwixt be upgraded to 1.0 beta 1 which is the latest in the Maven Ibiblio repository? If not, I think it is still better to chage the pom to specify 0.8-dev so when someone tries to use it, commons-betwixt won't be found, and then someone will realize that they have to copy your custom patched version into their Maven repo. If you don't want to change it, maybe you could at least put a comment in the pom. Upgrade version of commons-betwixt in pom.xml - Key: DDLUTILS-103 URL: http://issues.apache.org/jira/browse/DDLUTILS-103 Project: DdlUtils Type: Improvement Components: Core Reporter: Ken Weiner Assignee: Thomas Dudziak The pom.xml for building with Maven has common-betwixt at version 0.7 but it should be changed to 0.8-dev to match the version checked into the lib directory: dependency groupIdcommons-betwixt/groupId artifactIdcommons-betwixt/artifactId version0.8-dev/version /dependency Certain problems arise when using DdlUtils with an older version of commons-betwixt. For example, the unique element of the schema gets mistakenly added as a column. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DDLUTILS-56) Create JIRA components for DdlUtils project
[ http://issues.apache.org/jira/browse/DDLUTILS-56?page=comments#action_12370013 ] Ken Weiner commented on DDLUTILS-56: Having components per db implementation would make it much easier for people who use DdlUtils primarily with one database to track the issues related to their database. I often want to view the roadmap and then filter for certain databsaes to see what issues might affect me. Using environment for this limits the ability to do this because people may enter whatever they want for environment and filtering will be more difficult. Anyway, those are my 2 cents. Create JIRA components for DdlUtils project --- Key: DDLUTILS-56 URL: http://issues.apache.org/jira/browse/DDLUTILS-56 Project: DdlUtils Type: Task Reporter: Ken Weiner Assignee: Thomas Dudziak There are currently no components configured in JIRA for DdlUtils. This task is to create a set of components. For example, one could be created for each database implementation supported by DdlUtils. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DDLUTILS-57) Replace DateConverter's and TimeConverter's use of deprecated constructors
Replace DateConverter's and TimeConverter's use of deprecated constructors -- Key: DDLUTILS-57 URL: http://issues.apache.org/jira/browse/DDLUTILS-57 Project: DdlUtils Type: Improvement Reporter: Ken Weiner Assigned to: Thomas Dudziak Both DateConverter and TimeConverter use deprecated constructors of java.sql.Date and java.sql.Time respectively. This request is to replace the use of those constructors with a non-deprecated one. I am attaching a patch file that fixes both the DateConverter and TimeConverter to make use of the Calendar object to contruct the dates and times. This patch also adds a check to the convertToString methods to check the type of the object, throwing an exception if the object is not of the expected type. I also wrote some unit tests, DateConverterTest and TimeConverterTest to accompany these changes. Note: Before applying this patch, you could have called the convertFromString() methods with invalid text representations and the methods would have returned an unexpected date. Now with the use of Calendar, this won't happen since the Calendar instance has been set to not be lenient. See DateConverterTest.testConvertFromStringWithInvalidTextRep() and TimeConverter.testConvertFromStringWithInvalidTextRep(). These test methods do not pass with the current code, but do pass after applying this patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DDLUTILS-57) Replace DateConverter's and TimeConverter's use of deprecated constructors
[ http://issues.apache.org/jira/browse/DDLUTILS-57?page=all ] Ken Weiner updated DDLUTILS-57: --- Attachment: Converters-patch.txt New unit tests, DateConverterTest and TimeConverterTest as well as patches to DateConverter and TimeConverter. Replace DateConverter's and TimeConverter's use of deprecated constructors -- Key: DDLUTILS-57 URL: http://issues.apache.org/jira/browse/DDLUTILS-57 Project: DdlUtils Type: Improvement Reporter: Ken Weiner Assignee: Thomas Dudziak Attachments: Converters-patch.txt Both DateConverter and TimeConverter use deprecated constructors of java.sql.Date and java.sql.Time respectively. This request is to replace the use of those constructors with a non-deprecated one. I am attaching a patch file that fixes both the DateConverter and TimeConverter to make use of the Calendar object to contruct the dates and times. This patch also adds a check to the convertToString methods to check the type of the object, throwing an exception if the object is not of the expected type. I also wrote some unit tests, DateConverterTest and TimeConverterTest to accompany these changes. Note: Before applying this patch, you could have called the convertFromString() methods with invalid text representations and the methods would have returned an unexpected date. Now with the use of Calendar, this won't happen since the Calendar instance has been set to not be lenient. See DateConverterTest.testConvertFromStringWithInvalidTextRep() and TimeConverter.testConvertFromStringWithInvalidTextRep(). These test methods do not pass with the current code, but do pass after applying this patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DDLUTILS-59) Maven 2 Plugin for DdlToDatabase and DatabaseToDdl
Maven 2 Plugin for DdlToDatabase and DatabaseToDdl -- Key: DDLUTILS-59 URL: http://issues.apache.org/jira/browse/DDLUTILS-59 Project: DdlUtils Type: New Feature Reporter: Ken Weiner Assigned to: Thomas Dudziak This is a request for a Maven 2 plugin to offer the same functionality is available via the Ant tasks DdlToDatabase and DatabaseToDdl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DDLUTILS-55) HsqlDb PlatformInfo should not use delimited identifiers
HsqlDb PlatformInfo should not use delimited identifiers - Key: DDLUTILS-55 URL: http://issues.apache.org/jira/browse/DDLUTILS-55 Project: DdlUtils Type: Bug Reporter: Ken Weiner Assigned to: Thomas Dudziak Attachments: HsqlDbPlatform-patch.txt Currently, when creating tables using HSQLDB, double quotes () are used surrounding the table names in each CREATE TABLE statement. For example, CREATE TABLE person ... As a result, it isn't possible to write SQL without putting double quotes around tables names. For example, this statement doesn't work: select * from person; But this one does: select * from person; If useDelimitedIdentifiers in PlatformInfo is set to false, then double quotes will not surround the table names in CREATE TABLE statements and then SQL statements will work as expected (without having to include the double quotes). I will attach a patch for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DDLUTILS-55) HsqlDb PlatformInfo should not use delimited identifiers
[ http://issues.apache.org/jira/browse/DDLUTILS-55?page=all ] Ken Weiner updated DDLUTILS-55: --- Attachment: HsqlDbPlatform-patch.txt Path that sets useDelimitedIdentifiers to false for HSQLDB. HsqlDb PlatformInfo should not use delimited identifiers Key: DDLUTILS-55 URL: http://issues.apache.org/jira/browse/DDLUTILS-55 Project: DdlUtils Type: Bug Reporter: Ken Weiner Assignee: Thomas Dudziak Attachments: HsqlDbPlatform-patch.txt Currently, when creating tables using HSQLDB, double quotes () are used surrounding the table names in each CREATE TABLE statement. For example, CREATE TABLE person ... As a result, it isn't possible to write SQL without putting double quotes around tables names. For example, this statement doesn't work: select * from person; But this one does: select * from person; If useDelimitedIdentifiers in PlatformInfo is set to false, then double quotes will not surround the table names in CREATE TABLE statements and then SQL statements will work as expected (without having to include the double quotes). I will attach a patch for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DDLUTILS-56) Create JIRA components for DdlUtils project
Create JIRA components for DdlUtils project --- Key: DDLUTILS-56 URL: http://issues.apache.org/jira/browse/DDLUTILS-56 Project: DdlUtils Type: Task Reporter: Ken Weiner Assigned to: Thomas Dudziak There are currently no components configured in JIRA for DdlUtils. This task is to create a set of components. For example, one could be created for each database implementation supported by DdlUtils. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
