Commented by: @hvlad

a) what is connection character set ?
b) does you tried with isql ?

Commented by: Ann Harrison (awharrison)

Should a newly defined default apply to records that were stored with a null in that field?

Commented by: Yiannis Bourkelis (yiannis)

@vlad: On flamerobin the connection charset is set to NONE. I also tryied UTF8. Both return incorrect results.

I just tryied to run the query using isql and it works correctly.

@ann: I have never tryied that. Whenever I want to change the value of existing NULL columns, I execute an UPDATE statement first and then set the DEFAULT on that field to be sure.

Commented by: @asfernandes

> I just tryied to run the query using isql and it works correctly.

So? It's a problem with Flamerobin?

Commented by: Sean Leyne (seanleyne)

Case is closed, since the issue cannot be reproduced with Firebird tools/components.

Commented by: Yiannis Bourkelis (yiannis)

I will try to reproduce it with isql. How can I set the connection character set to NONE or UTF8?

Commented by: @asfernandes

isql -ch utf8

Commented by: Yiannis Bourkelis (yiannis)

Thank you Adriano,
I was able to reproduce it with isql:

Steps to reproduce:

1.run isql.exe -ch utf8 <path to attached database> -user SYSDBA -password <your password>

2. SQL> ALTER TABLE PRACTICEINFO ADD GOOGLE_PASSWORD VARCHAR(400) CHARACTER SET UTF8 DEFAULT 'MdX8fLruCUQ=' NOT NULL COLLATE UTF8;

3. exit;

Inspect the value of PRACTICEIFNO.GOOGLE_PASSWORD field. It is 'MdX' and not 'MdX8fLruCUQ='

Commented by: @asfernandes

Can you also test 2.5? I believe it's fixed there.

Commented by: Sean Leyne (seanleyne)

It seems that it is a real issue, but with older builds. So, re-opening pending review.

Commented by: Yiannis Bourkelis (yiannis)

I tested it on Firebird 2.5.2.26539 and it works as expected.