Issue Details (XML | Word | Printable)

Key: BAM-2260
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Ajay Sridhar [Atlassian]
Reporter: Ajay Sridhar [Atlassian]
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

Mysql integratio with Bamboo 2.0 Beta release 1 doesn't work

Created: 17/Feb/08 09:46 PM   Updated: 01/Apr/08 07:05 PM
Component/s: Database (Postgresql)
Affects Version/s: 2.0 DR, 2.0 beta 1
Fix Version/s: 2.0 beta 3, 2.0

Time Tracking:
Not Specified

Participants: Ajay Sridhar [Atlassian]
Since last comment: 45 weeks, 3 days ago
Number of comments: 1
Internal Priority: 1. Highest
Internal Work Bucket: Confirmed
Labels:


 Description  « Hide
In the Capablility_set table, we use a reserved word (KEY) to name a column - this doesn't go well with MYSQL so needs to be fixed!

As a result, the table creation fails -

2008-02-18 14:45:24,455 ERROR [btpool0-1] [SchemaExport] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'varchar(255), VALUE text, CAPABILITY_SET bigint, primary key (CAPABILITY_ID))' at line 1
2008-02-18 14:45:24,499 ERROR [btpool0-1] [SchemaExport] Unsuccessful: create table REQUIREMENT (REQUIREMENT_ID bigint not null, KEY varchar(255), REGEX_MATCH bit, READONLY_REQ bit, MATCH_VALUE text, REQUIREMENT_SET bigint, primary key (REQUIREMENT_ID))
2008-02-18 14:45:24,500 ERROR [btpool0-1] [SchemaExport] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'varchar(255), REGEX_MATCH bit, READONLY_REQ bit, MATCH_VALUE text, REQUIREMENT_S' at line 1
2008-02-18 14:45:24,564 ERROR [btpool0-1] [SchemaExport] Unsuccessful: alter table CAPABILITY add constraint FKEE341118A542349B foreign key (CAPABILITY_SET) references CAPABILITY_SET (CAPABILITY_SET_ID)
2008-02-18 14:45:24,564 ERROR [btpool0-1] [SchemaExport] Table 'mysql.CAPABILITY' doesn't exist


 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ajay Sridhar [Atlassian] added a comment - 25/Feb/08 06:42 PM
Fixed, the offending KEY column has been renamed to KEY_IDENTIFIER.