Open sliekens opened 9 years ago
You think this should just be a documentation add? Implicitly created ones are probably best handled by the database, but if someone wants to be explicit about them, they could potentially put them in the indexes folder and do all of the working against with the database to get them in inside the scripts.
I don't know. I'm still learning the difference between OneTime and AnyTime scripts, and when or why I should use one over the other. I raised this issue because I genuinely don't know where to put primary keys/unique constraints.
If the database implicitly creates those and you are not doing anything special for them, it's better to let the database handle those.
The wiki has a drop-create template for user-defined indexes, but fails to even mention implicit indexes that are created for primary keys/unique constraints. It's not clear if primary keys/unique constraints belong in the "indexes" folder.