List of Contributions

Javier Sagrera

Contact Details

My Content

1 to 16 of 16 total
Posted By Javier Sagrera Fri August 11, 2023 07:43 AM
Found In Egroup: Informix
\ view thread
Fix for idsdb00112743 is in. Next CSDK (4.50.xC11) should have it. If you can't wait until then try getting a CSDK special build through tech support. ------------------------------ Javier Sagrera ------------------------------
Posted By Javier Sagrera Wed August 09, 2023 06:49 AM
Found In Egroup: Informix
\ view thread
Add more than one character to the c1 row, like "aaöaa". Had not chance to look at the code yet, but I think the value used to calculate the string length for the conversion is wrong, it is not properly taken in count that the UTF8 'ö' (C3B6) will convert to just a single byte (F6) in 8859-15. Adding ...
Posted By Javier Sagrera Wed August 09, 2023 05:15 AM
Found In Egroup: Informix
\ view thread
Hi, Pretty sure there is something broken in FC10. /* d:\Infx\work\esql>set | grep LOCALE CLIENT_LOCALE=en_US.8859-15 DB_LOCALE=en_US.utf8 d:\Infx\work\esql> d:\Infx\work\esql>setinfx 450fc8 setting INFORMIX to csdk450fc8 d:\Infx\work\esql>f3 --test-- --test-- d:\Infx\work\esql>f3 ...
Posted By Javier Sagrera Tue August 08, 2023 01:57 PM
Found In Egroup: Informix
\ view thread
Hi, Yeap, 57372 is 0xE01C which is the code for UTF-8 (You can find the whole list in the $INFORMIXDIR/gls/cm/registry file). Your oncheck output shows you have the correct value for the 'ö' (0xC3B6) so something else must be going on here. I will try to run it on a Linux box but shouldn't ...
Posted By Javier Sagrera Tue August 08, 2023 12:01 PM
Found In Egroup: Informix
\ view thread
Ummmmm... Are you sure you have a 0xC3B6 on the database? I ran a quick test with 4.50.FC10 and I could query a 'ö' (0xC3B6) lvarchar in a UTF-8 db using CLIENT_LOCALE=en_US.8859-15. It gets converted to the expect 0xF6 on the client side. D:\Infx\ids1410>oncheck -pp testutf8:t1 256 addr stamp ...
Posted By Javier Sagrera Tue January 10, 2023 01:50 PM
Found In Egroup: Informix
\ view thread
Andreas is correct. Informix docker images are going to be published in the IBM Container registry (icr.io/informix).as IBM is moving away from hosting of Docker hub. As far as I know, next images will be based on 14.10.FC9 but I have no fix date yet. Hopefully it will happend in the ...
Posted By Javier Sagrera Wed October 20, 2021 12:16 PM
Found In Egroup: Informix
\ view thread
Hi, Looking at that docker it does looks like you are copying everything from the project dir into the container, so my guess is that the db2app64.dll will be also there. What about VC++ redistributable Maybe it is not the db2 dll but one of their dependecies that is missing. I think there are ...
Posted By Javier Sagrera Wed October 20, 2021 08:39 AM
Found In Egroup: Informix
\ view thread
Hi, Somehow I missed your latest message. db2app64.dll is the Db2 cli driver, all the DB2 .NET Providers use that underneath. It is part of the dataserver runtime libraries, it is included in one of the package dependencies (Net5.IBM.Dta.Db2) so it should be already in your system. It usually goes ...
Posted By Javier Sagrera Wed October 13, 2021 03:19 PM
Found In Egroup: Informix
\ view thread
Hi, EF 5.0 is quite old. Are you sure that is what you want to use? If so, there is no native EF provider from Informix, but you should be able to use the 'generic' IBM Data Server Provider for .NET. The IBM Data Server Provider can be used against Db2 and Informix. For Informix you need to use ...
Posted By Javier Sagrera Wed February 10, 2021 11:39 AM
Found In Egroup: Informix
\ view thread
I can reproduce the problem. I think there is a different in how the first GLS environment gets created from a "database .." to a "connect to". I guess the "connect to" is not initializing the environment properly so, when the ESQL code parses the statement with the (0xf6), it raises the 202 error. ...
Posted By Javier Sagrera Fri January 15, 2021 09:21 AM
Found In Egroup: Informix
\ view thread
You don't need to use a different constructor based on the value, just use the proper one all the time. My take is that is always better to use the correct data types from the application side and not assume the driver (or the server) will be able to convert the data. If your column is defined ...
Posted By Javier Sagrera Fri January 15, 2021 08:53 AM
Found In Egroup: Informix
\ view thread
Hi, Starting with CSDK 4.50.xC4, Informix .NET Core Provider compatible with .NET Core SDK/Runtime v3.1 is shipped for Windows x64 and Linux x86_64 platforms https://www.ibm.com/support/knowledgecenter/SSGU8G_14.1.0/com.ibm.cliapinode.doc/ids_net_core.htm Latest CSDK version is 4.50.FC5. It ...
Posted By Javier Sagrera Fri January 15, 2021 08:15 AM
Found In Egroup: Informix
\ view thread
Hi, I think the problem is cause by the method used to create the Interval parameter. IntervalDF valueInsert = new IntervalDF(totalSeconds, 0); Without any info about the Interval, the JDBC driver will create a DAY to FRACTION(5) so for a long value like '863999' the parameter will be sent to ...
Posted By Javier Sagrera Tue August 18, 2020 11:11 AM
Found In Egroup: Informix
\ view thread
So you got TSL working with GSkit, at least is a start. I suggested to copy 'net.iem' message file because the info you get with finderr is quite generic. Most of the time we return more info with the error than just the error description: informix@irk:/data/informix/IBM/4.50.FC4N/etc$ dbaccess ...
Posted By Javier Sagrera Tue August 18, 2020 10:22 AM
Found In Egroup: Informix
\ view thread
If you are getting that "cannot open net.iem" error you must have CSDK in a separate INFORMIXDIR than the server, so CSDK would be using OpenSSL and not GSKit. That's fine, but it means you will need to do the stuff to import the certificate from the server using OpenSSL (which you may already tried). ...
Posted By Javier Sagrera Mon August 17, 2020 10:09 AM
Found In Egroup: Informix
\ view thread
That extra "-" is one of the issues we found to be wrong in the documentation (which is currently 'under' review). With 14.10.FC4W1 and 4.50.FC4W1 you should use '.p12'. It is the extension server and client expect for the keystore as it has a pkcs12 inside. By default server will look for a '$ ...