You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jobtype names should be unique per parent jobqueue instead of globally across the whole system. This could allow jobqueue structures like
project 1
+- lighting
project 2
+- lighting
Unfortunately, this isn't entirely trivial because of the special case of jobqueues on the top level, which is signified by jobqueue_id=NULL. Different SQL servers treat NULL values differently inside of unique constraints – PostgreSQL treats them as always different (which is what the SQL standard says, but not very helpful for us in this case), SQL Server treats them as equal. Dunno about MySQL or SQLite.
The text was updated successfully, but these errors were encountered:
Hmm, I'd really like to avoid having to write in different behaviors per db. I wonder if we should rethink the approach our approach to 'global' some? We're likely to have this same issue in other areas where we need a global state and overrides.
guidow
added a commit
to guidow/pyfarm-master
that referenced
this issue
Nov 18, 2014
Jobtype names should be unique per parent jobqueue instead of globally across the whole system. This could allow jobqueue structures like
Unfortunately, this isn't entirely trivial because of the special case of jobqueues on the top level, which is signified by
jobqueue_id=NULL
. Different SQL servers treatNULL
values differently inside of unique constraints – PostgreSQL treats them as always different (which is what the SQL standard says, but not very helpful for us in this case), SQL Server treats them as equal. Dunno about MySQL or SQLite.The text was updated successfully, but these errors were encountered: