July 16, 2015 at 11:52 am
We have a SQL Server 2008R2 SP2 on Win2008R2. When we run the below query in Mgt Studio it returns results. When it is a prepared statement running via the application using the weblogic.jdbc.sqlserver.SQLServerDriver type 4 non-XA driver it doesn't return any results. The odd thing is when I search about this type 4 driver it doesn't say it supports SQL Server 2008 or R2 but I cannot find any newer driver..
I have done some searching and I cannot find out anything about any JDBC 4 type driver issues with query results. Does anyone have any suggestions?
select EmpID
, XID
from tablemane
where XID like 'PSCAL' + '[0-9][0-9]'
or XID like 'PSCAL' + 'c[1-9]'
or XID like 'PSCAL' + '[0-9][0-9][0-9]'
or XID like 'PSCAL' + '[0-9]c[1-9]'
order by XID;
July 16, 2015 at 12:10 pm
Markus (7/16/2015)
We have a SQL Server 2008R2 SP2 on Win2008R2. When we run the below query in Mgt Studio it returns results. When it is a prepared statement running via the application using the weblogic.jdbc.sqlserver.SQLServerDriver type 4 non-XA driver it doesn't return any results. The odd thing is when I search about this type 4 driver it doesn't say it supports SQL Server 2008 or R2 but I cannot find any newer driver..I have done some searching and I cannot find out anything about any JDBC 4 type driver issues with query results. Does anyone have any suggestions?
select EmpID
, XID
from tablemane
where XID like 'PSCAL' + '[0-9][0-9]'
or XID like 'PSCAL' + 'c[1-9]'
or XID like 'PSCAL' + '[0-9][0-9][0-9]'
or XID like 'PSCAL' + '[0-9]c[1-9]'
order by XID;
This:
select
EmpID,
XID
from
tablemane
where
XID like 'PSCAL' + '[0-9][0-9]'
or XID like 'PSCAL' + 'c[1-9]'
or XID like 'PSCAL' + '[0-9][0-9][0-9]'
or XID like 'PSCAL' + '[0-9]c[1-9]'
order by
XID;
can be written like this:
select
EmpID,
XID
from
tablemane
where
XID like 'PSCAL[0-9][0-9]'
or XID like 'PSCAL[1-9]'
or XID like 'PSCAL[0-9][0-9][0-9]'
or XID like 'PSCAL[0-9]c[1-9]'
order by
XID;
Try the second version from your application.
July 17, 2015 at 6:45 am
We figured out the issue and fixed it. Thanks for your response.
July 17, 2015 at 9:00 am
Markus (7/17/2015)
We figured out the issue and fixed it. Thanks for your response.
How did you fix the issue? Others may have the same problem and you solution may save them time solving their issue.
July 20, 2015 at 5:19 am
The query was being used in two different sql servers. One of the tables had the XID column as CHAR the other VARCHAR. It should have had the query with a % at the end of each statement. Self inflicted wound.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply