db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4091) Investigate "size_problem" column in MailJdbc terst
Date Thu, 12 Mar 2009 18:42:50 GMT
Investigate "size_problem" column in MailJdbc terst

                 Key: DERBY-4091
                 URL: https://issues.apache.org/jira/browse/DERBY-4091
             Project: Derby
          Issue Type: Task
          Components: Test
    Affects Versions:
            Reporter: Kathey Marsden
            Priority: Minor

In the MailJdbc test there is a table 
CREATE TABLE inbox (id bigint generated always as identity (start with 1,increment by 1),
					from_name varchar(64),
					to_name varchar(64),
					message clob(3M),
					date timestamp,
					folder_id Integer,
					to_delete smallint default 0,
					exp_date timestamp,
					attach_id smallint default 0,
					size_problem varchar(32672),
					CONSTRAINT inbox__pk PRIMARY KEY (id));

Which has a column "size_problem". We always insert into this column the value

								"This column is used only to by pass the space problem. If the problem still exists,
then we are going to "
										+ "have a serious issue here.*****************************************************************************************************");

Which seems to imply there is some bug  that manifests itself if we don't have this column,
but I don't see a bug reference.  It would be interesting to take the column out and see what

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message