Subject | Weirdness with blobs in a table. |
---|---|
Author | Sean Mathews |
Post date | 2004-06-14T14:43:03Z |
Hi All
FB 1.5 / WinXP Server
I am having some weirdness with a database I am creating. I have created a program that read MySQL metadata and creates the equivalent table on a FB Server, and copies the data. Most of the tables work fine (there are +- 30 tbales). Two tables are giving me problems, both have many blob fields (14 at the most). What happens is the table is created with no error complaint (a primary key is supplied). But when I check the data the first two fields are filled with 0's (for an integer field) and blank (for a character field). I can change this data, but it reverts to the way it was previously on a commit. One table has 57 various fields, the other only about 10. If I use the SQL my program generates to create the table, then create the table manually, it has the same effect, essentially a read only table. If I change the fields to Varchar(potentially truncating the data) it all works fine.
Help. Please. Or I'll kick my cat. Hard.
S
FB 1.5 / WinXP Server
I am having some weirdness with a database I am creating. I have created a program that read MySQL metadata and creates the equivalent table on a FB Server, and copies the data. Most of the tables work fine (there are +- 30 tbales). Two tables are giving me problems, both have many blob fields (14 at the most). What happens is the table is created with no error complaint (a primary key is supplied). But when I check the data the first two fields are filled with 0's (for an integer field) and blank (for a character field). I can change this data, but it reverts to the way it was previously on a commit. One table has 57 various fields, the other only about 10. If I use the SQL my program generates to create the table, then create the table manually, it has the same effect, essentially a read only table. If I change the fields to Varchar(potentially truncating the data) it all works fine.
Help. Please. Or I'll kick my cat. Hard.
S