Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM SQL » View Thread |
Messages 1 to 8 of 8 total |
UPDATE bug! Urgent! |
Thu, Dec 28 2006 1:10 PM | Permanent Link |
Ricardo Oliveira | Hi,
I have a problem with this query: UPDATE myTable SET myField = IF (myField = 'ABC' THEN '123' ELSE myField) Everything works fine until DBISAM finds a record where myField = '' or NULL. From that record on myField will always be null. For example: For this table... +---------+ | myField | +---------+ | ABC | | (NULL) | | ABC | The result will be... +---------+ | myField | +---------+ | 123 | | (NULL) | | (NULL) | I only have this problem since I updated to DBISAM 4.25 build 1 (Delphi 7). My program is full of queries like this one and I need to release an update before the end of the year. I need help urgently. Thanks, Ricardo Oliveira |
Thu, Dec 28 2006 5:02 PM | Permanent Link |
Steve Forbes Team Elevate | Hi Ricardo,
How about this? UPDATE myTable SET myTable = IF (myTable = 'ABC' OR myTable = NULL THEN '123' ELSE myTable) HTH -- Best regards Steve "Ricardo Oliveira" <RicardoREMOVETHISOliveira@jpmabreuANDTHIS.pt> wrote in message news:5AC5F91A-3B34-4B12-A4BA-A2F5E9A82BAA@news.elevatesoft.com... > Hi, > > I have a problem with this query: > > UPDATE myTable SET > myField = IF (myField = 'ABC' THEN '123' ELSE myField) > > Everything works fine until DBISAM finds a record where myField = '' or > NULL. From that record on myField will always be null. > For example: > > For this table... > +---------+ > | myField | > +---------+ > | ABC | > | (NULL) | > | ABC | > > The result will be... > +---------+ > | myField | > +---------+ > | 123 | > | (NULL) | > | (NULL) | > > I only have this problem since I updated to DBISAM 4.25 build 1 (Delphi > 7). > My program is full of queries like this one and I need to release an > update before the end of the year. > > I need help urgently. > > Thanks, > > Ricardo Oliveira |
Thu, Dec 28 2006 5:15 PM | Permanent Link |
"Robert" | "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message news:FF363C21-BC47-4CA4-B870-1F4127305EA9@news.elevatesoft.com... > Hi Ricardo, > > How about this? > OP states CLEARLY that "[his] program is full of queries like this one and I need to release an update before the end of the year." Probably the only solution is to go back to the prior version of DBISAM, unless Tim can produce a patch today. Robert |
Thu, Dec 28 2006 8:05 PM | Permanent Link |
"Jerry Hayes" | > unless Tim can produce a patch today.
Just curious here...is there anything TO patch? Or is the latest update just enforcing things that should have been enforced all along? |
Thu, Dec 28 2006 10:49 PM | Permanent Link |
"Robert" | "Jerry Hayes" <jhayes@nospam-connexability-dot-com> wrote in message news:75A155DC-6B1E-4846-A08A-55B23E0244D5@news.elevatesoft.com... >> unless Tim can produce a patch today. > > Just curious here...is there anything TO patch? > > Or is the latest update just enforcing things that should have been > enforced all along? > Uh? Read again the description of the problem. If the OP is correct (I can't confirm, I have not installed yet the latest version) DBISAM is changing the rules FOR SUBSEQUENT RECORDS once it finds the first null. How can that possibly be right? Robert |
Fri, Dec 29 2006 9:54 AM | Permanent Link |
"Jerry Hayes" | > Read again the description of the problem...
Of course, you're absolutely right, and that's what I get for picking something up mid-thread. BTW, whenever something like this happens from vendors, we always have a policy of reverting to known point (back to version xxx) rather than waiting for a patch. |
Fri, Dec 29 2006 10:21 AM | Permanent Link |
Ricardo Oliveira | Thank you all for your help.
I believe this is a bug in DBISAM because the behavior is not consistent (as Robert stated) although I would like to hear Tim about this one. Reverting to the previous installed version of DBISAM is not an option at this point because it also had a bug that was affecting the application. Ricardo Oliveira |
Fri, Dec 29 2006 3:08 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ricardo,
<< I have a problem with this query: UPDATE myTable SET myField = IF (myField = 'ABC' THEN '123' ELSE myField) Everything works fine until DBISAM finds a record where myField = '' or NULL. From that record on myField will always be null. >> It's a bug. I'll see if I can get a build 2 out today with a fix. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 09:18 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |