-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IBM.Data.DB2.iSeries DLL #15
Comments
@RoyC-Retail-Assist, can you help in this? Main problem that we have no testing environment for iSeries. |
@maxcoats - can you give me some details of what you are doing when you get the issue? what is the structure of the table you are trying to access etc. |
@RoyC-Retail-Assist could you confirm that recent linq2db.linqpad release works for you with iseries? |
I've actually had the same issue using the linqtodb4iseries provider but was able to fork and patch it to work for me. |
|
Even if it is not the reason - we should remove IBM.Data.DB2.iSeries.dll from linqpad integration and use version from GAC |
That's strange. It's one of fixes in 2.5.1 integration. Maybe you use previous version? If it is recent version - fill issue here with bad generated code sample |
c:\ProgramData\LINQPad path does not contain a drivers directory for me. |
Well, maybe linqpad stores them somewhere else on your machine. |
After driver change to v12 same error :( |
I will install iseries provider tomorrow and try to debug it tomorrow without database.
|
@maxcoats The iSeries provider has been tested against iAccess V 7 Release 0 SI55797. I'm guessing that XML column type was introduced after V6. @MaceWindu I'll do some debugging later this evening on the LinqPad stuff as I would expect it to work ok on my machine. |
Ahh, sorry I missed that. Will have to try and build with my patched version of linqtodb4iseries. Thanks everyone! |
Confirmed this is straight from IBM's website The 7.1 .NET Provider includes these enhancements: Support for the IBM i XML data type |
Glad to hear that it is solved. |
Any thoughts on this?
The text was updated successfully, but these errors were encountered: