L. van der Hart
Member
As soon as I use an object type that is subtyped from another type (using the 'under' keyword), my version of PL/SQL Developer becomes instable. I can reproduce this as follows:
1) Create a type called TYPE_SUPER:
'create or replace TYPE TYPE_SUPER is object ( field1 number(10) )'
2) Create a subtype called TYPE_SUB:
'create or replace TYPE TYPE_SUB under TYPE_SUPER ( field2 varchar2(100) )'
Compiling this will succeed most of the times. But as soon as I use one of these types in a package function, or even in a member function of the type itself, it will show errors like 'Access violation at address 7C911689 in module ntdll.dll'.
If I modify my types from an independent SQL window (using File > New > SQL Window), these problems don't show up, but I can't use code hinting either in that case for type members/functions etc).
This doesn't happen when I don't use type inheritance, so it could be something with object dependencies.
Has someone experienced this before? Some help would be highly appreciated.
Regards,
L. vd Hart
1) Create a type called TYPE_SUPER:
'create or replace TYPE TYPE_SUPER is object ( field1 number(10) )'
2) Create a subtype called TYPE_SUB:
'create or replace TYPE TYPE_SUB under TYPE_SUPER ( field2 varchar2(100) )'
Compiling this will succeed most of the times. But as soon as I use one of these types in a package function, or even in a member function of the type itself, it will show errors like 'Access violation at address 7C911689 in module ntdll.dll'.
If I modify my types from an independent SQL window (using File > New > SQL Window), these problems don't show up, but I can't use code hinting either in that case for type members/functions etc).
This doesn't happen when I don't use type inheritance, so it could be something with object dependencies.
Has someone experienced this before? Some help would be highly appreciated.
Regards,
L. vd Hart
