db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DDLUTILS-51) BOOLEANINT for MS-SQL desires TINYINT, but uses SMALLINT
Date Sat, 26 Nov 2005 18:55:55 GMT
    [ http://issues.apache.org/jira/browse/DDLUTILS-51?page=comments#action_12358562 ] 

Thomas Dudziak commented on DDLUTILS-51:
----------------------------------------

The output simply means that the table oci_schedules.schd_state  already existing in the database,
has a column whose corresponding JDBC type is TINYINT. And the default JDBC mapping for BOOLEANINT
(which isn't a JDBC type) is SMALLINT, so an altering of the column type has happened.

> BOOLEANINT for MS-SQL desires TINYINT, but uses SMALLINT
> --------------------------------------------------------
>
>          Key: DDLUTILS-51
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-51
>      Project: DdlUtils
>         Type: Bug
>  Environment: WinXP Pro, SQL-Server 2000, java 1.4.2
>     Reporter: Colin Ritchie
>     Assignee: Thomas Dudziak
>     Priority: Minor

>
> Columns for MS-SQL with Type BOOLEANINT get the following error when using the ant task
writeSchemaToDatabase:
> [ddlToDatabase] INFO: Altering column oci_schedules.schd_state
> [ddlToDatabase] INFO:   desired = Column [name=schd_state; javaName=null; type=TINYINT;
typeCode=-6; size=null; required=false; primaryKey=false; autoIncrement=false; defaultValue=null;
precisionRadix=0; scale=0]
> [ddlToDatabase] INFO:   current = Column [name=schd_state; javaName=null; type=SMALLINT;
typeCode=5; size=5; required=false; primaryKey=false; autoIncrement=false; defaultValue=null;
precisionRadix=5; scale=0]
> The following is a snippet of my configuration file:
> <table name="oci_schedules">
>   <column name="schd_state" primaryKey="false" required="false" type="BOOLEANINT"
autoIncrement="false"/>
> </table>

-- 
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


Mime
View raw message