comment on

Ah, you were looking for a DEFERRABLE CONSTRAINT, which postpones the constraint-validation to the end of a transaction.

So, you'd do (again, postgres):

create table         tree (
   f_node_id   int primary key
 , f_parent_id int
 , f_name      text
 , f_sort      float
 , constraint tree_parent_sort_uniq_idx unique (f_parent_id, f_sort) d
+eferrable
);
[download]

This lets you mess about with non-unique states for the duration of a transaction. The constraint (here: uniqueness) is only then enforced.

I can't imagine MariaDB does not have this functionality but I can't find it in the documentation. (I looked for DEFERRED or DEFERRABLE. The MariaDB docs list 'DEFERRED' as a reserved word but I see no functionality associated with it.)

In reply to Re^5: [OT] MySQL recalibrating a sort-index by erix
in thread [OT] MySQL recalibrating a sort-index by LanX

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks