Svein Erling Tysvaer wrote:

> Andrew Guts wrote:
>
>> I need to convert some of my database fields into UTF-8. So I wrote and
>> run operator by operator the script below:
>> --------------------------------------------------------
>> alter table cms_wiki
>> add u_name varchar(100) character set UTF8,
>> add u_title varchar(100) character set UTF8,
>> add u_description blob sub_type 1 character set UTF8,
>> add u_text blob sub_type 1 character set UTF8;
>>
>> commit;
>>
>> update cms_wiki set
>> u_name = name, u_title = title, u_text = text, u_description =
>> description; /* Here it hangs */
>>
>
> Have you tried splitting the update statement into two, three or four
> separate update statements? That way, you could find if it was a problem
> with the blobs specifically and if the problem appeared whether you
> tried updating one or two blob fields in the same statement.
>

No, I haven't. Do you mean field by field or record by record? Thank you
for the idea, I'll try it.

> I have no idea whether it is possible to convert character sets for text
> blobs this way or not, but there's no way updating 52 records should
> take more than 30 minutes (well, theoretically if each blob is huge and
> you use an extremely slow internet connection and the BDE, I suppose it
> could be that slow ;o) and you should at least have been given an error
> message. I expect that there is no other transaction active that
> accesses this table when you try to do the update?
>
>

I do not expect problems when converting any character set into unicode.
The database is small and each the blob contains one fragment of a web
page. Each fragment is about 1-2 pages in a browser. I've run the
statements using isql.exe, local connection (the server is the same
computer - my desktop. There are no clients attached).

I've tried that script on the production server (RHEL 4, Tomcat 5.0 as
the one client using local connection). Tomcat had been shut down and
the script was launched using isql locally. It hanged right at the first
table (100% CPU load and busy HDD), which had structure similar to
cms_wiki, in spite of that table had been updated successfully on my
local computer earlier.

The database had been running under Firebird 1.5 and then upgraded to
2.0 using backup/restore. Could it be the cause of the problem?

> Set
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>