How secure is Oracle against system modifications

#1

Hello,

I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to
version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Was is possible to execute the upper statement in Oracle 5?

Thank you,
Norbert

#2

On May 26, 3:42*am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,

I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to
version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

#3

On May 26, 3:42*am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,

I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to
version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

#4

On May 26, 3:42*am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,

I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to
version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

#5

On May 26, 3:42*am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,

I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to
version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

#6

"fitzjarrell (AT) cox (DOT) net" <oratune (AT) msn (DOT) com> wrote in
news:aa03f96d-060d-4726-9b61-25edba3a77ac (AT) 34g2000hsf (DOT) googlegroups.com...

On May 26, 3:42 am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,
I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

* Oracle 5 did not have constraints - these were introduced in version 6.
This statement is therefore only backwards compatible starting with version 6.

Cheers,
Roelof Schierbeek

#7

"fitzjarrell (AT) cox (DOT) net" <oratune (AT) msn (DOT) com> wrote in
news:aa03f96d-060d-4726-9b61-25edba3a77ac (AT) 34g2000hsf (DOT) googlegroups.com...

On May 26, 3:42 am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,
I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

* Oracle 5 did not have constraints - these were introduced in version 6.
This statement is therefore only backwards compatible starting with version 6.

Cheers,
Roelof Schierbeek

#8

"fitzjarrell (AT) cox (DOT) net" <oratune (AT) msn (DOT) com> wrote in
news:aa03f96d-060d-4726-9b61-25edba3a77ac (AT) 34g2000hsf (DOT) googlegroups.com...

On May 26, 3:42 am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,
I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

* Oracle 5 did not have constraints - these were introduced in version 6.
This statement is therefore only backwards compatible starting with version 6.

Cheers,
Roelof Schierbeek

#9

"fitzjarrell (AT) cox (DOT) net" <oratune (AT) msn (DOT) com> wrote in
news:aa03f96d-060d-4726-9b61-25edba3a77ac (AT) 34g2000hsf (DOT) googlegroups.com...

On May 26, 3:42 am, Norbert Pürringer <thalio... (AT) graffiti (DOT) net> wrote:

Quote:

Hello,
I would like to know, how secure Oracle is against modifications in
names of system tables or system table columns from version to version.

Do you think, that a select statement like

"SELECT COL.COLUMN_NAME FROM USER_CONS_COLUMNS COL, USER_CONSTRAINTS
CON WHERE CON.TABLE_NAME = {0} AND COL.CONSTRAINT_NAME =
CON.CONSTRAINT_NAME AND CON.CONSTRAINT_TYPE='P'"

will work in a version Oracle 15 too?

Depends upon how Oracle 15 has its data dictionary configured, doesn't
it. The current data dictionary views (the ones spanning who knows
how many releases before now) haven't changed much over the years, so
I would *expect* such a query to function. But, I have no
clairevoyant abilities so your guess is as good as anyones.

Quote:

Was is possible to execute the upper statement in Oracle 5?

As far as I know, yes, but you'd need a copy of Oracle 5 to verify
that. And I don't understand why some functionality which MAY have
been introduced in Oracle 6 causes you a problem now. It's expected
that many queries will NOT be backward compatible.

Quote:

Thank you,
Norbert

David Fitzjarrell

* Oracle 5 did not have constraints - these were introduced in version 6.
This statement is therefore only backwards compatible starting with version 6.

Cheers,
Roelof Schierbeek

#10

On 27 May, 17:09, "R. Schierbeek" <byteNospamL... (AT) gmail (DOT) com> wrote:

Quote:

* Oracle 5 did not have constraints - these were introduced in version 6.
This statement is therefore only backwards compatible starting with version 6.

Cheers,
* *Roelof Schierbeek

This may be of some interest: http://en.wikipedia.org/wiki/Oracle_...nical_timeline