Re: [Firebird-devel] Different collation ID for altered computed column

2015-09-13 Thread Claudio Valderrama C.
> -Original Message- > From: Jirí Cincura [mailto:j...@cincura.net] > Sent: Viernes, 11 de Septiembre de 2015 6:10 > > Hi, > > can somebody explain this behavior? Tested on FB 2.5.4 and > 2.5.3 x64 SC. > > CREATE TABLE T_TRANSLATION_META ( > F_TRM_ID BIGINT NOT NULL, >

Re: [Firebird-devel] Different collation ID for altered computed column

2015-09-13 Thread Jiří Činčura
On Mon, Sep 14, 2015, at 03:43, Claudio Valderrama C. wrote: > The collation is stored in rdb$relation_fields not in rdb$fields. I'm not interested in actual value. I'm just wondering why the two values differ after alter, given the alter changed nothing. > I sent an email to the master of hell

Re: [Firebird-devel] Different collation ID for altered computed column

2015-09-11 Thread Adriano dos Santos Fernandes
On 11/09/2015 06:10, Jiří Činčura wrote: > Hi, > > can somebody explain this behavior? Tested on FB 2.5.4 and 2.5.3 x64 SC. > > CREATE TABLE T_TRANSLATION_META ( > F_TRM_ID BIGINT NOT NULL, > F_TRM_CODE VARCHAR(512) CHARACTER SET UTF8 NOT NULL COLLATE > UNICODE_CI >

Re: [Firebird-devel] Different collation ID for altered computed column

2015-09-11 Thread Jiří Činčura
On Fri, Sep 11, 2015, at 16:49, Adriano dos Santos Fernandes wrote: > Some bug fixed (intentionally or not) in v3. Should I put it to tracker? -- Mgr. Jiří Činčura Independent IT Specialist -- Firebird-Devel mailing