Re: 7.1 update breaks behavior of persistent fields!!

From: Mark Edington \(Borland\) (medington_at_nolunchmeat.com)
Date: 05/12/04 

Date: Wed, 12 May 2004 12:35:45 -0700

"Michael Rodriguez" <mike@nospamforme.com> wrote in message
news:40a14336$1@newsgroups.borland.com...

> I am curious to see how he justifies releasing an update that literally
> breaks people's applications.

Sorry about the delay in commenting here. My newsreader was giving me fits
trying to post yesterday and I've been running around like a headless
chicken dealing with this issue.

Clearly many folks (and I'll put myself at the top of the list),
underestimated the ramifications of the change that was made to to enforce
the size matching. I was a little hesitent at the time I made the change,
but I really had no idea how common it it is for folks to have this
situation in their applications.

As it stands, the fix is not helping anyone because it has adversely
affected so many applications (and clearly that was not the intention of the
change), so the arguments about whether or not the DB code should enforce
the size matching are somewhat moot. We don't want to be introducing
changes in a patch (or even a point release) that have this effect. Period.

The original TClientDataset defect that prompted the change (QC#3874) can
and will be fixed in a different way.

We are are urgently working on a remedy for this situation and I will be
posting more information regarding that as soon as it is available.

For folks who installed the patch and are affected by this it is my
recomendation that you simply revert the related files from the original
Delphi 7 CD. There are only a handful of fixes in those files anyway. I'll
outline what to copy from the CD below.

By way of defense for the change, I would point out that the size checking
code introduced is actually a slightly more relaxed version of the checking
that was done in Delphi 4 and prior releases. So it's not something
completely new. On the other hand, it is certainly valid for the size of a
persistent field to be larger than the size of the underlying field in the
case where the data is read-only and at the very least that provision should
have been coded in as well. In any case, it is my opinion that the "fix"
should be completely removed and the code restored to the way it was in
Delphi 7.0.

Finally, I would like to offer my most sincere apology to you and the other
folks who were impacted by this issue.

Mark

------------------

Steps for reverting DB.pas and related binaries from the Delphi 7.0 CD:

<D7> = Delphi 7 install directory

CD File Destination on disk
\Install\System32\dbrtl70.bpl -> \Windows\System32
\Install\Program Files\Borland\Delphi7\Lib\DB.dcu -> <D7>\Lib
\Install\Program Files\Borland\Delphi7\Lib\Debug\DB.dcu -> <D7>\Lib\Debug
\Install\Program Files\Borland\Delphi7\Source\Vcl\DB.pas -> <D7>\Source\Vcl

Relevant Pages

  • Re: Is Borland QA *really* lacking?
    ... web services isn't something that has really ever been well ... > ability to create SOAP clients was only added in a Delphi 6 update. ... The new IW Standard, IW Data, IW Client Side, and IW Control pages provide ... IntraWeb components for developing Web-based applications. ...
    (borland.public.delphi.non-technical)
  • Re: Announcing CodeGear RAD Studio 2007
    ... compelling health applications to be quickly and easily created. ... to continue down this path -- the ability to continue using Crystal Reports ... Delphi, not Delphi.Net. ... applications to students rather than records management to administrators, ...
    (borland.public.delphi.non-technical)
  • Re: Delphi2005 BETA
    ... I take it it's a matter of Borland ... Delphi 2005 - Compact Framework Support? ... find that very few have plans to develop CF applications. ... How can I transition my development teams to .NET (ASP.NET ranks at the ...
    (borland.public.delphi.non-technical)
  • Re: Signaling for a running application
    ... One written in Deplhi, the other in c#. ... For what it's worth, in your original post, among other things the apparent use of Delphi jargon was a definite impediment to understanding what it is exactly you're trying to do. ... A common technique for connecting two disparate applications would be simply to use regular network i/o. ...
    (microsoft.public.dotnet.framework)
  • Re: Borland/DevCO has lost its innovative power
    ... Borland/DevCO is a business. ... Folks talk about all the features Delphi should have and how dead it ... Folks just assume that what they want is what everyone wants. ...
    (borland.public.delphi.non-technical)