I am seeing a major problem related to CLOBs as I move from EDB 1 to
EDB2. I often change tables in code. In this case I want to change a
varchar field to CLOB. This works fine if the table is changed in
EDB1. In EDB2 I get a 600 cannot rename file error for the .EDBBlb
file "Cannot create a file when that file already exists".

Michael,

<< I am seeing a major problem related to CLOBs as I move from EDB 1 to
EDB2. I often change tables in code. In this case I want to change a varchar
field to CLOB. This works fine if the table is changed in EDB1. In EDB2 I
get a 600 cannot rename file error for the .EDBBlb file "Cannot create a
file when that file already exists". >>

Which build of 2.02 are you using ?  Also, just to confirm - you alter a
table, and then change the VARCHAR column to a CLOB data type, and then the
error occurs, correct ?

--
Tim Young
Elevate Software
www.elevatesoft.com

On Fri, 2 Oct 2009 18:04:04 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< I am seeing a major problem related to CLOBs as I move from EDB 1 to
>EDB2. I often change tables in code. In this case I want to change a varchar
>field to CLOB. This works fine if the table is changed in EDB1. In EDB2 I
>get a 600 cannot rename file error for the .EDBBlb file "Cannot create a
>file when that file already exists". >>
>
>Which build of 2.02 are you using ?  Also, just to confirm - you alter a
>table, and then change the VARCHAR column to a CLOB data type, and then the
>error occurs, correct ?

Build 15. Yes on attempting to change VARCHAR to CLOB the error occurs
only in EDB 2.

Michael,

<< Build 15. Yes on attempting to change VARCHAR to CLOB the error occurs
only in EDB 2. >>

I can't reproduce this here.  Here's what I'm using:

ALTER TABLE "customer2"
ALTER COLUMN "Company" AS CLOB COLLATE "ANSI"

When customer2 looks like this to start with:

CREATE TABLE "customer2"
(
"CustNo" FLOAT,
"Company" VARCHAR(30) COLLATE "ANSI",
"Addr1" VARCHAR(30) COLLATE "ANSI",
"Addr2" VARCHAR(30) COLLATE "ANSI",
"City" VARCHAR(15) COLLATE "ANSI",
"State" VARCHAR(30) COLLATE "ANSI",
"Zip" VARCHAR(10) COLLATE "ANSI",
"Country" VARCHAR(20) COLLATE "ANSI",
"Phone" VARCHAR(15) COLLATE "ANSI",
"FAX" VARCHAR(15) COLLATE "ANSI",
"TaxRate" FLOAT,
"Contact" VARCHAR(20) COLLATE "ANSI",
"LastInvoiceDate" TIMESTAMP,
CONSTRAINT "PrimaryKey" PRIMARY KEY ("CustNo")
)

--
Tim Young
Elevate Software
www.elevatesoft.com

On Fri, 2 Oct 2009 18:16:13 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< Build 15. Yes on attempting to change VARCHAR to CLOB the error occurs
>only in EDB 2. >>
>
>I can't reproduce this here.  Here's what I'm using:
>
>ALTER TABLE "customer2"
>ALTER COLUMN "Company" AS CLOB COLLATE "ANSI"
>
>When customer2 looks like this to start with:
>
>CREATE TABLE "customer2"
>(
>"CustNo" FLOAT,
>"Company" VARCHAR(30) COLLATE "ANSI",
>"Addr1" VARCHAR(30) COLLATE "ANSI",
>"Addr2" VARCHAR(30) COLLATE "ANSI",
>"City" VARCHAR(15) COLLATE "ANSI",
>"State" VARCHAR(30) COLLATE "ANSI",
>"Zip" VARCHAR(10) COLLATE "ANSI",
>"Country" VARCHAR(20) COLLATE "ANSI",
>"Phone" VARCHAR(15) COLLATE "ANSI",
>"FAX" VARCHAR(15) COLLATE "ANSI",
>"TaxRate" FLOAT,
>"Contact" VARCHAR(20) COLLATE "ANSI",
>"LastInvoiceDate" TIMESTAMP,
>CONSTRAINT "PrimaryKey" PRIMARY KEY ("CustNo")
>)

I didn't have the COLLATE "ANSI" part but adding that had no effect.
The field I am changing is 250 characters. That seems to be the only
other difference.

Michael,

<< I didn't have the COLLATE "ANSI" part but adding that had no effect. The
field I am changing is 250 characters. That seems to be the only other
difference. >>

I'm trying this with the latest 2.03, so I'll have to try it in 2.02 and see
if there's something that was fixed as a side-effect of something else.

--
Tim Young
Elevate Software
www.elevatesoft.com