Constraint indexes are created differently than non-constraint schema indexes. Yet only one index can exist for a particular label/property key combination at a time. Therefor you have to drop the ordinary index before you can create a constraint on the same label/property key. A constraint otherwise implies an index.
-- Chris Vest System Engineer, Neo Technology [ skype: mr.chrisvest, twitter: chvest ] On 02 Feb 2014, at 01:57, Michael Hunger <[email protected]> wrote: > if it already exists it is not created again > > and yes for unique constraints we create a companion index > > On Sun, Feb 2, 2014 at 12:28 AM, Aran Mulholland > <[email protected]> wrote: >> If I use the following command: >> >> CREATE INDEX ON :Player(name) >> >> or >> >> CREATE CONSTRAINT ON pl:Player >> ASSERT pl.name IS UNIQUE >> >> and the index or constraint already exists, does it hurt to issue the >> command twice? >> >> Also, does creating a constraint implicitly create an index? >> >> Copied from the excellent slides at >> http://www.slideshare.net/markhneedham/optimizing-cypher (page 12) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Neo4j" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
