Subject Re: [firebird-support] Timestamp conversion issue
Author Alex Castillo
Post date 2016-04-07T04:26:31Z
I've no doubt this is a bug for the linux release. It should be filtering the string literals before doing the conversion as it does on Windows.

The way I've solved was by creating a global temporary table and copying the values from a view, converting the varchar to time. So now, when I perform DATA + TIME = TIMESTAMP in a right way. This is not optimal, but it does work meantime the issue can be evaluated by the firebird team.

Thanks & regards,
 
_______________________________
I'm free, I use GNU/Linux.
Close your Windows,
Open your mind.


De: "Mark Rotteveel mark@... [firebird-support]" <firebird-support@yahoogroups.com>
Para: firebird-support@yahoogroups.com
Enviado: Martes, 5 de abril, 2016 6:20:53
Asunto: Re: [firebird-support] Timestamp conversion issue

 
On 2016-04-05 10:47, Alex Castillo acr_korn@...
[firebird-support] wrote:
> Hello everyone,
>
> I'm having some issues with a stored procedure. This is a legacy
> development, so the time was stored in a varchar field and the date
> in
> a timestamp field.
>
> The issue stills happens after the upgrade from 2.1.5 to 2.1.7 on
> linux open suse 11.4 x64, classic engine. However, this is not
> happening on my development machine using Windows XP. Even on my
> development environment I've restored the database to 2.1.5 using
> classic and super, but the issue is not being reproduced there, It
> seems to be a linux specific issue. In both cases I'm using
> FlameRobin
> as client.

Could you show a sample of the time values? As far as I know Firebird
use platform specific time conversion functions. This means that
non-SQL-standard formats can fail or succeed depending on the platform
(and maybe regional settings).

Mark