This is second email. Can somebody confirm, that there is Access
Violation when we insert (or append) first row into empty dataset ?
(or I missed something?)
You can use attached program.
TIA
L.
program testOldValue;
{$mode objfpc}{$H+}
uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
On Thu, 9 Jun 2011, LacaK wrote:
This is second email. Can somebody confirm, that there is Access Violation
when we insert (or append) first row into empty dataset ?
(or I missed something?)
You can use attached program.
Is the problem only with sqlite ?
Michael.
This is second email. Can somebody confirm, that there is Access
Violation when we insert (or append) first row into empty dataset ?
(or I missed something?)
You can use attached program.
Is the problem only with sqlite ?
No, I can reproduce it also for example with MySQL.
But exception is
Here is attached debug output with {$DEFINE DSDebug}.
It seems, that exception is related to Append/Insert (it does not depend
if dataset is empty before or not) followed by accesing OldValue
...
Setting current record to0
Post: Browse mode set
Active buffer requested. Returning:0
exception at
On Thu, 2011-06-09 at 11:49 +0200, LacaK wrote:
Here is attached debug output with {$DEFINE DSDebug}.
It seems, that exception is related to Append/Insert (it does not depend
if dataset is empty before or not) followed by accesing OldValue
Can't you just post the backtrace?
Joost.
--
My
May be like this ?
Thanks.
Laco.
On Thu, 2011-06-09 at 11:49 +0200, LacaK wrote:
Here is attached debug output with {$DEFINE DSDebug}.
It seems, that exception is related to Append/Insert (it does not depend
if dataset is empty before or not) followed by accesing OldValue
Can't you
Hi,
I committed a possible fix in rev. 17704. Please test.
Michael.
On Thu, 9 Jun 2011, LacaK wrote:
May be like this ?
Thanks.
Laco.
On Thu, 2011-06-09 at 11:49 +0200, LacaK wrote:
Here is attached debug output with {$DEFINE DSDebug}.
It seems, that exception is related to
Very similar to my fix, which I did minute ago.
We can more cleanup code by removing unneeded parts.
Please look at attached patch.
Thanks
L.
PS1: Yes it fixes AV
PS2: But still remains OldValue=null problem (see me 1st email)
Hi,
I committed a possible fix in rev. 17704. Please test.
On Thu, 9 Jun 2011, LacaK wrote:
Very similar to my fix, which I did minute ago.
We can more cleanup code by removing unneeded parts.
Please look at attached patch.
Applied the patch.
Thanks
L.
PS1: Yes it fixes AV
Good :-)
PS2: But still remains OldValue=null problem (see me 1st
Applied the patch.Thanks a lot What email is that, I only find a message about AV ?Message with subject TField.OldValue (today some minutes before my first message with subject "Inserting first record"-Laco.
___
fpc-devel maillist -
10 matches
Mail list logo
