delphi - '0.0' is not a valid timestamp when accessing OldValue of TClientDataSet's TDateField -


When I use the following code in a new inserted record in a TClientDataSet: 

  CdsMyDateField Old Value & lt; & Gt; Zero

I get an error message: 

  '0.0' is not a valid timestamp '

Delphi Looking at the VCL's code, TDateTime tries to change this value, which results in an exception as the value (tap) is an invalid date time, but as I compare the variants I The type will return, which will be tapped in this case, but it does not happen, its Instead I get this exception.

I know that I can only check whether before DataSet.State = dsInsert values ​​compare, like state = every old current has a tap, but I have to understand that the old value is only all Rather than returning the taps in the fields why try to change the value when state = DSINRST

Anyone give me some light?

FWI, I have participated in this problem and this gave me reason many headaches My opinion: Incompatible behavior So, because of this reason alone I class it as a bug. This is also a bug because the IMHO is a ridiculous exception to reading an asset and does not keep with the intent of properties (at least with the theory of surprises). I hope the old man should be assigned, did not take exception to reading (besides, the fact that some issues exist for a long time or not, whether it is a bug or not, does not show anything about it .)

(Edit: Updating my answer with more information, along with our solution, has been posted on QC report besides :)

< P> This was the only problem in the app Micro heavy use Detanet / Claintdetsets. Although the actual problem is not with the client data set, but with the timestamp verification assignment in SysUtils, it apparently incorrectly validates a timestamp with 0.0 values ​​as invalid.

Therefore workaround / fix is ​​therefore for SysUtils and validation routine, and not specifically, in the validity rule "ValidateTimeStamp ()", the time portion is properly compiled & lt; 0 but the date part is erroneously compared & lt; = 0.

As a result, a (valid) 0.0 time time value is sometimes converted to a timestamp with datepart = 0, and when this value is re-verified (such as when data The dataset is read from the field as shown here and in the QC report), an exception (by mistake) has been raised so to change the recognition for the date part of the timestamp, to make them easy to use, the strict TClientDataset Door This was a solution to the highlighted problem.

Here our workaround is based on Delphi 7.1 

  (* SysUtils.pas line 10934 (Delphi 7.1) *) (**) (* OK - Timestamp value 0.0 Wrongly named as invalid) * (* D7.1 *) (* Walter Prince, originally settled in May 2005, submitted on June 4, 2009 *) Process Validated DataTump (Conf. Timestamp: TTEMSTAMP) ); (TimeStamp.Date & lt; = 0 TimeStamp.Date & lt; 0 *) ConvertErrorFmt (@SInvalidTimeStamp); , [TimeStamp.Date, Timestamp .Phil.]); End;

Comments

Post a Comment

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

I'm having trouble overriding a ModelForm save method. I get this error I'm: Exception type: TypeErier Exception Value: Save () found an unexpected keyword argument 'committed' My intentions include a form 3 fields Submit several values ​​for, then create an object for each combination of those areas, and to save each object file models.py class collarsult type (models.Model): id = model. AutoField (db_column = 'icontact_result_code_type_id', primary_key = true) callResult = models.ForeignKey ( 'CallResult', db_column = 'icontact_result_code_id') campaign = models.ForeignKey ( 'campaign', db_column = 'icampaign_id') CALLTYPE = models.ForeignKey ( 'CALLTYPE', db_column = 'icall_type_id') agent = models.BooleanField (db_column = 'bagent', default = true) teamLeader = models.BooleanField (db_column = 'bTeamLeader', default = true) active = models.BooleanField (db_column = Django.form...
Read more

html - CSS autoheight, but fit content to height of div -

I have a div in which there are three children- div in the left and middle div: float: left while true: float: true because it is my layout Actually will spoil, I've used ClearFix Hack: .cf {zoom: 1; }. Cf: First,. Cf: {content: ""; Display: Table; }. Cf: After {clear: both; } It still works, but I want to be the right div an indicator. So it should fill 100% of the parent unit of height. How can I complete this? PS is the full code: & Lt; / Div & gt; & Lt; Div class = "mobile_content" & gt; & Lt; H5 & gt; {{Data.titel}} & lt; / H5> & Lt; Table & gt; & Lt; TR & gt; & Lt; Th & gt; Komponist: & lt; / Th & gt; & Lt; TD & gt; {{Data.komponist}} & lt; / TD & gt; & Lt; / TR & gt; & Lt; TR & gt; & Lt; Th & gt; Instrument: & lt; / Th & gt; & Lt; TD & gt; {{Data.instrumente}} & lt; / TD & gt; & Lt; / TR & gt;...
Read more

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -

I have been trying to use Qt5 multimedia to record audio with QAudioInput, however, when I see If QAudioInput is started, it increases the master volume of my sound device to 100%. How can I prevent QAudioInput from changing the master volume? My current development platform is Linux with PalsAdio (with flat audio disabled). How can I use QAudioInput : QAudioDeviceInfo device_info = QAudioDeviceInfo :: defaultInputDevice (); QAudio format format; Format.setSampleRate (44100); Format.setChannelCount (1); Format.setSampleSize (16); Format.setCodec ("Audio / PCM"); Format.setSampleType (QAudioFormat :: SignedInt); Format.setByteOrder (QAudioFormat :: LittleEndian); Std :: cout & lt; & Lt; Device_info.deviceName (). ToUtf8 (). ConstData () & lt; & Lt; Std :: endl; QAudioInput * default_device = new QAudioInput (device_info, format); QIODevice * default_io_device = default_device-> Start (); a QAudioInput.setVolume () method is not you I ...
Read more