Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 14 of 14 total
Thread AV when altering constraint
Mon, Sep 15 2008 11:33 AMPermanent Link

Marcin
I am terrible sorry for all that mess. By accident I put and "END" inside my script and
this caused that large part of it was not executed at all. I think I will have to post
less and double check everything first. Sorry for the mess once again.

Marcin.
Tue, Sep 16 2008 5:59 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Marcin,

<< I just tried build 5.
The error is still there. Now I get "ElevateDB Error #900 An error occurred
with the statement at line 240 and column 25 (Access violation at address
004CBC63 in module 'edbsrvr.exe'. Read of address 65727289)". >>

Are you sure that you posted the same catalog that you're using in your
tests ?  I cannot reproduce this at all here using your catalog and B5.

<< With code to delete about 50 tables 30 scripts and 10 triggers. While
debugging, when only few tables or functions exists, I have to step on every
exception although I wrote code to handle it. It is very annoying! I hardly
can use ElevateDB Manager now. >>

We'll be adding an option to turn off the "stop on exception" functionality
shortly.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Sep 16 2008 7:03 AMPermanent Link

Marcin
Tim,

Thank you for all your help. I did not use the same catalog because I was working on it in
the meantime. The error was raised in my current database. This bug was raised for any
table constraints alteration. I was not able to fix it but when I create new database and
try to run script on that database everything is fine. I did not had any important data in
my old database so it was not a problem for me. Everything works fine for me now (I did
recompile ElevateDB Manager and added an option to disable "stop on all exceptions"
functionality).

There is one small thing that I would like to point because it may be an error when you
reuse database component with multiple sessions

file: edbcomps.pas
method: TEDBDatabase.CheckSessionName

  if (NewSession <> nil) and (NewSession <> FSession) then
     begin
     if (FSession <> nil) then begin
        FSession.RemoveDatabase(Self);
        FSession.RemoveFreeNotification(Self);  <- this line should be added to pair with
this line |
     end;                                                                               
                                            |
     FSession:=NewSession;                                                              
                                 |
     FSession.FreeNotification(Self);
<------------------------------------------------------------------|
     FSession.AddDatabase(Self);
     end;

Once again thank you for all your help.

Marcin.
Tue, Sep 16 2008 8:54 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Marcin,

<< Thank you for all your help. I did not use the same catalog because I was
working on it in the meantime. The error was raised in my current database.
This bug was raised for any table constraints alteration. I was not able to
fix it but when I create new database and try to run script on that database
everything is fine. I did not had any important data in
my old database so it was not a problem for me. >>

It may have something to do with this issue:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.01&type=f&incident=2763

One of the side effects of this issue was that altering a constraint
repeatedly could result in some internal links in the catalog between the
target primary key and the altered foreign key to accumulate.  Thus, when
you went to drop the foreign key, it may have experienced issues.  If you
had repeatedly altered the foreign key that was causing you this issue with
2.01 B4 or earlier, then this is most likely the cause.  2.01 B5 no longer
has this issue, of course.

<< Everything works fine for me now (I did recompile ElevateDB Manager and
added an option to disable "stop on all exceptions" functionality). >>

Cool.  I'll be adding that for the next minor release along with some
options for disabling saving of the state, and some new options for
specifying the sorting of objects.

<< There is one small thing that I would like to point because it may be an
error when you reuse database component with multiple sessions >>

Good catch.  I will make sure to add this fix for 2.02.

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

« Previous PagePage 2 of 2
Jump to Page:  1 2
Image