×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Luke,
Fortunately for me my comparisons were doing a >= and a <= so I was able
to just use the BETWEEN keyword. But I was lucky. Most times this would
not have worked out. This does seem like quite an obvious bug that should
have been picked up in testing.
Thanks
Bryce Martin
Programmer/Analyst I
Ext. 4777
Luke Gerhardt <lgerhardt@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
11/10/2008 07:44 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
wdsci-l@xxxxxxxxxxxx
cc
Subject
Re: [WDSCI-L] Odd problem in SQL/free
Bryce,
No, unfortunately I have not any idea how to fix this auto-'correcting'
issue. The only solution I have employed so far is to go back to SEU
and make the changes I need there. It really stinks that I have to
resort to that, but I have no better ideas at this point.
Any ideas, IBM? Are qualified and 100% legitimate SQL statements no
longer supported by your software? Is there a 'break working SQL'
option somewhere that I overlooked and should turn off? *rolls eyes*
--Luke
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
