Forum Discussion
sstevens
8 years agoNew Contributor
Hey Everybody
I am using Oracle RDBMS
I incorporated a workaround for the issue using a regular expressions in the assertion where the expected date result was being checked
i.e.
2008-09-12 12:00:00*
The assertion was specifically hardcoding the .0 at the end of the string:
2008-09-12 12:00:00.0
Which IS NOT smart in my opinion anyway---
For my purposes this is ok
The real issue with this was that Ready API JDBC response was including the ".0" at the end of the string when running on Machine X and when getting the same JDBC response on Machine Y the ".0" WAS NOT showing up
The wildcard for the .0 takes care of that issue for my circumstances
But I never really got a great answer as to WHY this would happen
richie
8 years agoCommunity Hero
hi,
difference in environmental config im guessing between the 2 machines.
same versions of readyapi!, java, .jar driver files for the oracle thin driver?
gotta be something like that right?
cheers,
richie
difference in environmental config im guessing between the 2 machines.
same versions of readyapi!, java, .jar driver files for the oracle thin driver?
gotta be something like that right?
cheers,
richie