Re: WHERE condition lost from conditional unique index
| От | David G Johnston |
|---|---|
| Тема | Re: WHERE condition lost from conditional unique index |
| Дата | |
| Msg-id | 1402080986366-5806365.post@n5.nabble.com обсуждение исходный текст |
| Ответ на | WHERE condition lost from conditional unique index (jake fagan <jakeofagan@gmail.com>) |
| Список | pgsql-novice |
jake fagan wrote > Why would the migration work on my development but not on Jenkins? The only obvious problem I can come up with is that your development environment and the source for Jenkins do not have the same codebase. Did you ever attempt to create this particular index without the where clause - and now just recently converted it into a partial? I doubt that Jenkins is silently ignoring the WHERE clause...an incorrect source file is more likely. > Am I applying the unique index correctly to begin with? Yes, though it is a "partial unique index" since you are using a where clause. David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/WHERE-condition-lost-from-conditional-unique-index-tp5806355p5806365.html Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
В списке pgsql-novice по дате отправления: