Subject RE: [firebird-support] Weirdness with blobs in a table. - Remail
Author Sean Mathews
> what query? I see no query. show it to me.
> Alan

Perhaps I am using the wrong words here. The table creation SQL, which was in the original email. It creates a table with the problems I describe. It is two SQL statements that my program generates then runs. I can (and have) run these statements with a number of different Firebird tools like Marathon etc, and the resulting table always has the same flaws as described in the original email.

S

create table trans1(
ID integer not null,
NAME varchar(60) not null,
SZ_ID smallint not null,
TYPE_ID smallint not null,
SZ_TYPE_SUB varchar(30),
HDT smallint not null,
HDN smallint not null,
HDM smallint not null,
HDH smallint not null,
INIT varchar(60) not null,
SPD varchar(120) not null,
SDF varchar(120) not null,
ARF varchar(120),
DARM varchar(120),
FRCH varchar(120) not null,
SA varchar(255),
SQ varchar(255),
SVS varchar(30) not null,
SVSF smallint,
SVSR smallint,
SVSW smallint,
AB varchar(50) not null,
S1 smallint,
S2 smallint,
S3 smallint,
S4 smallint,
S5 smallint,
S6 smallint,
SK blob sub_type 1 segment size 128,
FTS blob sub_type 1 segment size 128,
CLIM varchar(120) not null,
ORG blob sub_type 1 segment size 128,
CHR varchar(35) not null,
CHR_VALUE double precision not null,
TR varchar(120) not null,
AL varchar(60) not null,
ADV varchar(80),
DESCR blob sub_type 1 segment size 128,
DESCRG blob sub_type 1 segment size 128,
DESCR_C blob sub_type 1 segment size 128,
DESCR_SA blob sub_type 1 segment size 128,
DESCR_SK blob sub_type 1 segment size 128,
DESCR_FTS blob sub_type 1 segment size 128,
DESCR_CHR blob sub_type 1 segment size 128,
DESCR_CNS blob sub_type 1 segment size 128,
DESCR_TRA blob sub_type 1 segment size 128,
DESCR_CCA blob sub_type 1 segment size 128,
DFIRST smallint not null,
DVERSION varchar(32) not null,
SOURCE_NAME varchar(32) not null,
SOURCE_URL varchar(32) not null,
SOURCE_EMAIL varchar(32) not null,
SOURCE_ID integer not null,
CREATED date not null,
MODIFIED date not null,
MOD_ID integer not null,
DELETED_FLAG smallint not null);




alter table trans1 add constraint PK_TRANS1 primary key (ID);




[Non-text portions of this message have been removed]