- Thank you received: 0
possible regression (already seen bug)?
- usp_rol
- Topic Author
- Offline
- User
-
Less
More
3 years 5 months ago #14546
by usp_rol
possible regression (already seen bug)? was created by usp_rol
Hi all
due to introduction of materialized views we've upgraded our driver from 1.4.0.3522 to 1.4.0.3572 hopping to get rid of the mentioned "Undefined table" error (now just getting another sadly).
But to make things worst, existing functionality (with 1.4.0.3522) does not seem to work with 1.4.0.3572 (was already discussed pgnp cannot determine output columns for procedure )
the call (as stated here in forum) to a procedure ends in
also a
does not solve as a reboot of the machine does also not.
any help in further identify the issue would be greatly appreciated!
(we're running MSSQL 2017 with Postgresql 9.4)
due to introduction of materialized views we've upgraded our driver from 1.4.0.3522 to 1.4.0.3572 hopping to get rid of the mentioned "Undefined table" error (now just getting another sadly).
But to make things worst, existing functionality (with 1.4.0.3522) does not seem to work with 1.4.0.3572 (was already discussed pgnp cannot determine output columns for procedure )
the call (as stated here in forum) to a procedure ends in
Code:
OLE DB provider "PGNP" for linked server "[LINKED_SERVER]" returned message "Cannot determine output columns for procedure [function_name]".
also a
Code:
EXEC('pgnp_refreshmetadata(''[schema]'',''[function_name]'')') AT [linked_server]
does not solve as a reboot of the machine does also not.
any help in further identify the issue would be greatly appreciated!
(we're running MSSQL 2017 with Postgresql 9.4)
Please Log in or Create an account to join the conversation.
- admin
- Offline
- Admin
-
Less
More
- Thank you received: 7
3 years 5 months ago #14547
by admin
Replied by admin on topic possible regression (already seen bug)?
Could you email the CREATE statement for the problematic procedure to our Support? We will try to reproduce and fix the issue.
Thank you!
Thank you!
Please Log in or Create an account to join the conversation.
- admin
- Offline
- Admin
-
Less
More
- Thank you received: 7
3 years 5 months ago - 3 years 5 months ago #14548
by admin
Replied by admin on topic possible regression (already seen bug)?
Hi,
thank you for the additional details! We were able to reproduce the issue with Postgres 10.5, and fixed it in build 3577. The following queries are working fine now:
EXEC ('f_stored_proc') AT PG10;
SELECT * FROM OPENQUERY(PG10, 'SELECT 1 FROM f_stored_proc()');
However, the following is returning "either the object has no columns or the current user does not have permissions" error (as expected):
SELECT * FROM OPENQUERY(PG10, 'f_stored_proc()');
We sent link to the fixed module.
thank you for the additional details! We were able to reproduce the issue with Postgres 10.5, and fixed it in build 3577. The following queries are working fine now:
EXEC ('f_stored_proc') AT PG10;
SELECT * FROM OPENQUERY(PG10, 'SELECT 1 FROM f_stored_proc()');
However, the following is returning "either the object has no columns or the current user does not have permissions" error (as expected):
SELECT * FROM OPENQUERY(PG10, 'f_stored_proc()');
We sent link to the fixed module.
Last edit: 3 years 5 months ago by admin.
Please Log in or Create an account to join the conversation.
Time to create page: 0.153 seconds