Subject | Mac OSX and Varchar |
---|---|
Author | ew8ew8 |
Post date | 2005-02-15T21:19:21Z |
I am porting an application from Windows to Mac OSX. I ran into a
few database converstion issues I have gotton around, but my newest
issue is the following:
org.firebirdsql.FBSQLException: Resource Exception. Unrecognized
transaction.
Same query works on Windows FB (both 1.5).
Seems to have to do with the data table structure:
CREATE TABLE CLOZE_LESSON (
LESSON_ID INTEGER NOT NULL,
TARGET_WORD VARCHAR(50),
LESSON_TYPE INTEGER,
SEGMENT_TEXT_1 VARCHAR(5000),
SEGMENT_TEXT_2 VARCHAR(5000),
SEGMENT_TEXT_3 VARCHAR(5000),
SEGMENT_TEXT_4 VARCHAR(5000),
SEGMENT_TEXT_5 VARCHAR(5000),
SEGMENT_TEXT_6 VARCHAR(5000),
SEGMENT_TEXT_7 VARCHAR(5000),
SEGMENT_TEXT_8 VARCHAR(5000),
BLANK_LINE_NR INTEGER,
ANSWER_CHOICE_1 VARCHAR(100),
ANSWER_CHOICE_2 VARCHAR(100),
ANSWER_CHOICE_3 VARCHAR(100),
ANSWER_CHOICE_4 VARCHAR(100),
CORRECT_ANSWER INTEGER,
PHRASE VARCHAR(500),
SKILL_TYPE INTEGER,
CENTERING VARCHAR(50),
CONSTRAINT PK_CLOZE_LESSON PRIMARY KEY (LESSON_ID)
);
If I select * from CLOZE_LESSON, I will get the error. If I only
select some fields it will give me the results. It seems to have to
do with too much data in the row. I seem to be able to get around
it by CASTING it to a smaller VARCHAR.
eg. SELECT CAST(SEGMENT_TEXT_1 as VARCHAR(100)) ...
I shouldn't have to though, I thought that trim may solve my
problem,
but I am having problems getting the UDFs to work on OSX 10.3.
(I realize the table is ugly, but sometimes you have to deal with
what was there)
Any help would be appreciated.
Thanks
Eric
few database converstion issues I have gotton around, but my newest
issue is the following:
org.firebirdsql.FBSQLException: Resource Exception. Unrecognized
transaction.
Same query works on Windows FB (both 1.5).
Seems to have to do with the data table structure:
CREATE TABLE CLOZE_LESSON (
LESSON_ID INTEGER NOT NULL,
TARGET_WORD VARCHAR(50),
LESSON_TYPE INTEGER,
SEGMENT_TEXT_1 VARCHAR(5000),
SEGMENT_TEXT_2 VARCHAR(5000),
SEGMENT_TEXT_3 VARCHAR(5000),
SEGMENT_TEXT_4 VARCHAR(5000),
SEGMENT_TEXT_5 VARCHAR(5000),
SEGMENT_TEXT_6 VARCHAR(5000),
SEGMENT_TEXT_7 VARCHAR(5000),
SEGMENT_TEXT_8 VARCHAR(5000),
BLANK_LINE_NR INTEGER,
ANSWER_CHOICE_1 VARCHAR(100),
ANSWER_CHOICE_2 VARCHAR(100),
ANSWER_CHOICE_3 VARCHAR(100),
ANSWER_CHOICE_4 VARCHAR(100),
CORRECT_ANSWER INTEGER,
PHRASE VARCHAR(500),
SKILL_TYPE INTEGER,
CENTERING VARCHAR(50),
CONSTRAINT PK_CLOZE_LESSON PRIMARY KEY (LESSON_ID)
);
If I select * from CLOZE_LESSON, I will get the error. If I only
select some fields it will give me the results. It seems to have to
do with too much data in the row. I seem to be able to get around
it by CASTING it to a smaller VARCHAR.
eg. SELECT CAST(SEGMENT_TEXT_1 as VARCHAR(100)) ...
I shouldn't have to though, I thought that trim may solve my
problem,
but I am having problems getting the UDFs to work on OSX 10.3.
(I realize the table is ugly, but sometimes you have to deal with
what was there)
Any help would be appreciated.
Thanks
Eric