Skip to content
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

Closed
maxcoats opened this issue Nov 9, 2018 · 18 comments
Closed

IBM.Data.DB2.iSeries DLL #15

maxcoats opened this issue Nov 9, 2018 · 18 comments
Milestone

Comments

@maxcoats
Copy link

maxcoats commented Nov 9, 2018

image

Any thoughts on this?

@sdanyliv
Copy link
Member

sdanyliv commented Nov 9, 2018

@RoyC-Retail-Assist, can you help in this? Main problem that we have no testing environment for iSeries.

@RoyC-Retail-Assist
Copy link

@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.

@MaceWindu
Copy link
Contributor

@RoyC-Retail-Assist could you confirm that recent linq2db.linqpad release works for you with iseries?

@maxcoats
Copy link
Author

maxcoats commented Nov 9, 2018

I've actually had the same issue using the linqtodb4iseries provider but was able to fork and patch it to work for me.

@MaceWindu
Copy link
Contributor

MaceWindu commented Nov 9, 2018

I think I know the reason. For some reason we ship iseries v13 assembly with linqpad integration, but it expects v12. As quickfix try to remove or replace it with v12 assembly under c:\ProgramData\LINQPad\Drivers\DataContext\ root well, IBM should learn how to version their assemblies

@maxcoats
Copy link
Author

maxcoats commented Nov 9, 2018

image

@MaceWindu
Copy link
Contributor

Even if it is not the reason - we should remove IBM.Data.DB2.iSeries.dll from linqpad integration and use version from GAC

@RoyC-Retail-Assist
Copy link

I'm getting a different problem when it is populating the tables.

image

I'll get the source and try to triage what is going on but it won't be until Monday.

@MaceWindu
Copy link
Contributor

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

@maxcoats
Copy link
Author

maxcoats commented Nov 9, 2018

c:\ProgramData\LINQPad path does not contain a drivers directory for me.

@MaceWindu
Copy link
Contributor

MaceWindu commented Nov 9, 2018

Well, maybe linqpad stores them somewhere else on your machine.
for me it's
c:\ProgramData\LINQPad\Drivers\DataContext\4.0\linq2db.LINQPad (f19f8aed7feff67e)\IBM.Data.DB2.iSeries.dll
c:\ProgramData\LINQPad\Drivers\DataContext\5.0\linq2db.LINQPad (f19f8aed7feff67e)\IBM.Data.DB2.iSeries.dll

@maxcoats
Copy link
Author

maxcoats commented Nov 9, 2018

After driver change to v12 same error :(

@MaceWindu
Copy link
Contributor

I will install iseries provider tomorrow and try to debug it tomorrow without database.
Could you provide some details on versions you use to confirm that we all work with same versions:

  • linqpad
  • linq2db.linqpad
  • iSeries Access for Windows driver

@maxcoats
Copy link
Author

maxcoats commented Nov 9, 2018

linqpad v5.31.00
linq2db.linqpad v2.5.1

image

@RoyC-Retail-Assist
Copy link

@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.

@maxcoats
Copy link
Author

maxcoats commented Nov 9, 2018

Ahh, sorry I missed that. Will have to try and build with my patched version of linqtodb4iseries.

Thanks everyone!

@maxcoats
Copy link
Author

maxcoats commented Nov 9, 2018

Confirmed this is straight from IBM's website
https://www-01.ibm.com/support/docview.wss?uid=isg3T1027163

The 7.1 .NET Provider includes these enhancements:

Support for the IBM i XML data type
Support for longer SQL schema names
New property to configure the ConcurrentAccessResolution
Support for multi-row UPDATE, DELETE, and MERGE using the iDB2Command.AddBatch method
Class interfaces and technical information is now integrated with Visual Studio

@maxcoats maxcoats closed this as completed Nov 9, 2018
@MaceWindu
Copy link
Contributor

MaceWindu commented Nov 10, 2018

Glad to hear that it is solved.
@RoyC-Retail-Assist It would be great if you could update your provider readme to mark v7.1 as min version requirement, or even do it in code to throw exception with explanatory text.

@MaceWindu MaceWindu added this to the Release 2.5.2 milestone Nov 11, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants