Re: Help with a optimization problem

On Apr 28, 3:02 am, dombrooks <dombro...@xxxxxxxxxxx> wrote:
one possibility, depending on version, is to create an OR view of this
data using CAST... MULTISET ... SELECT ... ORDER BY.

That view could possibly contain an ordered array of attribute pairs
which you could then do a straight comparison on the ordered array of
the incoming set of values.

However, this approach will not make up for the fact that the OP is
suggesting bad design. Objects and object style constructs belong in
the application layer and should not be stored in the database.

A good old fashioned parameter table with parameter names in one
column and values in another will do the trick. The application layer
can easily pivot the parameters for one set into a single row
structure if desired.

IMHO -- Mark D Powell --

.