| Subject | Re: Type of context variables changed in FB2.1.2? |
|---|---|
| Author | ainpoissee |
| Post date | 2009-07-11T19:36:47Z |
--- In firebird-support@yahoogroups.com, Dmitry Yemanov <dimitr@...> wrote:
I did another quick test - connecting to 2.1.2 with FlameRobin (ANSI version) and executing select statement
SELECT * FROM TAB_Users WHERE(UPPER(UserName) = CURRENT_USER)
worked OK (the record of the current user were found). So perhaps there is something weird going on in ON CONNECT triggers - ie the character set isn't "assignet" at that time jet? But it worked in FB2.1.0 so something has changed since then...
ain
>The character set is the same in both FB2.1.0 and FB2.1.2 - the DB were restored from the same backup on both servers.
> > But the user name is there and if I use "Trim(CURRENT_USER)" as opposed to just "CURRENT_USER" then it is found with FB2.1.2 too. So it looks like trailing spaces issue (CHAR vs VARCHAR)?
>
> IIRC, the data type hasn't been changed. The only explanation I have in
> mind is that it could be character set related.
I did another quick test - connecting to 2.1.2 with FlameRobin (ANSI version) and executing select statement
SELECT * FROM TAB_Users WHERE(UPPER(UserName) = CURRENT_USER)
worked OK (the record of the current user were found). So perhaps there is something weird going on in ON CONNECT triggers - ie the character set isn't "assignet" at that time jet? But it worked in FB2.1.0 so something has changed since then...
ain