Hello everyone,
I have a proxy table in IQ (12.7) that points to another one in ASE(15.0). The one in ASE has several datetime columns. The corresponding IQ datatype for datetime is timestamp and the proxy table displays those values totally different and invalid.
Example of values from ASE :
id date_value
1 2012-09-18 09:06:13
2 2012-09-18 09:06:13
3 2012-09-18 09:06:13
4 2012-09-18 09:06:13
5 2012-09-18 09:06:13
Values displayed in ProxyTable in IQ :
id date_value
1 3203-10-23 16:51:03
2 3203-10-23 16:51:03
3 3203-10-23 16:51:03
4 3203-10-23 16:51:03
5 3203-10-23 16:51:03
Does anyone know why this strange conversion happens and perhaps a proper way to fix it.
One solution would be to store the actual date as a varchar (after a proper conversion so that it holds the date to the millisecond) but that's quite a hack.
Addon : This only happens when proxy tables are involved. Bulk insert (into location) works fine between ASE -> IQ.
Thank you,
Sorin
I have a proxy table in IQ (12.7) that points to another one in ASE(15.0). The one in ASE has several datetime columns. The corresponding IQ datatype for datetime is timestamp and the proxy table displays those values totally different and invalid.
Example of values from ASE :
id date_value
1 2012-09-18 09:06:13
2 2012-09-18 09:06:13
3 2012-09-18 09:06:13
4 2012-09-18 09:06:13
5 2012-09-18 09:06:13
Values displayed in ProxyTable in IQ :
id date_value
1 3203-10-23 16:51:03
2 3203-10-23 16:51:03
3 3203-10-23 16:51:03
4 3203-10-23 16:51:03
5 3203-10-23 16:51:03
Does anyone know why this strange conversion happens and perhaps a proper way to fix it.
One solution would be to store the actual date as a varchar (after a proper conversion so that it holds the date to the millisecond) but that's quite a hack.
Addon : This only happens when proxy tables are involved. Bulk insert (into location) works fine between ASE -> IQ.
Thank you,
Sorin