#1421 "call current value for ..." returns null string, if called before "call next value for ..."

[Luciano Joublanc]

"call current value for mycounter", if executed before "next value for mycounter" returns a null string. It should return the current value, I assume. This is through the DBManager GUI on 2.3.3.

If executed after a 'next value for ...', in the same DBManager session, it appears to work correclty.

[Fred Toussi]

This is not a bug. CURRENT VALUE means the most recent NEXT VALUE used by this session in this transaction. For example, if other sessions are getting NEXT VALUE at the same time, it would not change the CURRENT VALUE in this session.

[Luciano Joublanc]

Thanks for your patience ; this should be closed as invalid. I apologise, I don't have access to the sql spec.