Hi Tim,

I need to be able to set a unique constraint on a table but I also need
one of the fields (multi-field constraint) to be sorted in descending
order. EDB Manager automatically makes each field an ASC sort. This
can't be done currently (unless I am missing something) either
programmatically or via the EDB Manager,

Meanwhile, I can't create an index to do the same thing as I cannot
make the index UNIQUE, which is also necessary for this particular
table.

Could this option, either being able to select the sort order of a
field -and/or- being able to create a UNIQUE index, be included in
ElevateDB (especially in the EDB Manager)?

Thanks for a great product!

--
Jan Ferguson

Oops...sorry. Using EDB v2.03 build 4.

--

J.B. Ferguson wrote:

> Hi Tim,
>
> I need to be able to set a unique constraint on a table but I also
> need one of the fields (multi-field constraint) to be sorted in
> descending order. EDB Manager automatically makes each field an ASC
> sort. This can't be done currently (unless I am missing something)
> either programmatically or via the EDB Manager,
>
> Meanwhile, I can't create an index to do the same thing as I cannot
> make the index UNIQUE, which is also necessary for this particular
> table.
>
> Could this option, either being able to select the sort order of a
> field -and/or- being able to create a UNIQUE index, be included in
> ElevateDB (especially in the EDB Manager)?
>
> Thanks for a great product!

Dang...I can't get my fingers to work right. I *MEANT* v2.04 build 4
(in other words, the most recent version!)

--

J.B. Ferguson wrote:

> Hi Tim,
>
> I need to be able to set a unique constraint on a table but I also
> need one of the fields (multi-field constraint) to be sorted in
> descending order. EDB Manager automatically makes each field an ASC
> sort. This can't be done currently (unless I am missing something)
> either programmatically or via the EDB Manager,
>
> Meanwhile, I can't create an index to do the same thing as I cannot
> make the index UNIQUE, which is also necessary for this particular
> table.
>
> Could this option, either being able to select the sort order of a
> field -and/or- being able to create a UNIQUE index, be included in
> ElevateDB (especially in the EDB Manager)?
>
> Thanks for a great product!

Jan


What about using a check constraint and then you can use SQL, if necessary via a custom function.

Roy Lambert [Team Elevate]

Roy,

Thanks...

I could look into doing something like that but I was hoping for a
crisp and clean solution (just a mouse click or so.)  They (constraints
and indices) each have part of what I need to do...just hoping Tim
could allow either one to do the "other part".

--
Jan


Roy Lambert wrote:

> What about using a check constraint and then you can use SQL, if
> necessary via a custom function.

Jan


Just a thought.

There's nothing to stop you having a UNIQUE constraint and a separate index with the descending field.

Roy Lambert [Team Elevate]

Roy,

Duh! I couldn't see the forest through the trees. Of course! I don't
know why I was thinking that the index was relying on the sort order of
the data for uniqueness. Of course it isn't.

Sometimes you just get too close to a problem to see the obvious.
Thanks for the kick in the right direction.
--
Jan


Roy Lambert wrote:

> There's nothing to stop you having a UNIQUE constraint and a separate
> index with the descending field.