[
http://jira.codehaus.org/browse/MRM-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-894:
-----------------------------
Fix Version/s: 1.1.x
we'll have to look into some appropriate mappings
> Archiva MySQL bit datatype incompatible
> ---------------------------------------
>
> Key: MRM-894
> URL: http://jira.codehaus.org/browse/MRM-894
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.0, 1.0.1, 1.0.2, 1.1
> Environment: Centos 5.1 (2.6.18-53.e15)
> MySQL 5.0.22
> Java 1.6
> Reporter: Mark Jeffery
> Fix For: 1.1.x
>
>
> The tables are created with data-type BIT to represent boolean type fields.
> Before MySQL 5.0.3, BIT was a synonym for TINYINT(1) which works fine.
> However 5.0.3 and later versions of MySQL treat the BIT datatype differently.
> This leads to problems with all the sql fields that are supposed to represent
> boolean values. It becomes a big mess.
> An example is the column PERMANENT in a lot of the tables.
> Also the FROM_PARENT and TRANSITIVE columns in ARCHIVA_DEPENDENCY.
> When changing the column data-type in MySQL for existing data, the conversion
> of the actual data does not take place correctly because it was not inserted
> correctly in the first place.
> Would it not be possible to change the data-types in the code to boolean or
> another data-type so that when the tables are created in MySQL they have
> columns that represent boolean values.
> This also appears in Continuum.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
