search condition evaluates to TRUE are included in the result set. Be careful with possible NULL outcomes: if you negate a NULL expression with NOT, the result will still be NULL and the row will not pass

tasks are scheduled on the server, which differs from other DBeaver products. As a result, task outcomes are stored exclusively on the server. To access these results on a local machine, download them

tasks are scheduled on the server, which differs from other DBeaver products. As a result, task outcomes are stored exclusively on the server. To access these results on a local machine, download them

several principles in mind: • Implicit conversions should never have surprising or unpredictable outcomes. • There should be no extra overhead in the parser or executor if a query does not need implicit Example 11.3. Setting up a Partial Unique Index Suppose that we have a table describing test outcomes. We wish to ensure that there is only one “suc- cessful” entry for a given subject and target combination for insertion will either insert or update. Unless there are unrelated errors, one of those two outcomes is guaranteed. If a conflict originates in another transaction whose effects are not yet visible

several principles in mind: • Implicit conversions should never have surprising or unpredictable outcomes. • There should be no extra overhead in the parser or executor if a query does not need implicit Example 11.3. Setting up a Partial Unique Index Suppose that we have a table describing test outcomes. We wish to ensure that there is only one “success- ful” entry for a given subject and target combination for insertion will either insert or update. Unless there are unrelated errors, one of those two outcomes is guaranteed. If a conflict originates in another transaction whose effects are not yet visible

several principles in mind: • Implicit conversions should never have surprising or unpredictable outcomes. • There should be no extra overhead in the parser or executor if a query does not need implicit Example 11.3. Setting up a Partial Unique Index Suppose that we have a table describing test outcomes. We wish to ensure that there is only one “suc- cessful” entry for a given subject and target combination for insertion will either insert or update. Unless there are unrelated errors, one of those two outcomes is guaranteed. If a conflict originates in another transaction whose effects are not yet visible

several principles in mind: • Implicit conversions should never have surprising or unpredictable outcomes. • There should be no extra overhead in the parser or executor if a query does not need implicit Example 11.3. Setting up a Partial Unique Index Suppose that we have a table describing test outcomes. We wish to ensure that there is only one “suc- cessful” entry for a given subject and target combination for insertion will either insert or update. Unless there are unrelated errors, one of those two outcomes is guaranteed. If a conflict originates in another transaction whose effects are not yet visible

several principles in mind: • Implicit conversions should never have surprising or unpredictable outcomes. • There should be no extra overhead in the parser or executor if a query does not need implicit Example 11.3. Setting up a Partial Unique Index Suppose that we have a table describing test outcomes. We wish to ensure that there is only one “suc- cessful” entry for a given subject and target combination for insertion will either insert or update. Unless there are unrelated errors, one of those two outcomes is guaranteed. If a conflict originates in another transaction whose effects are not yet visible

several principles in mind: • Implicit conversions should never have surprising or unpredictable outcomes. • There should be no extra overhead in the parser or executor if a query does not need implicit Example 11.3. Setting up a Partial Unique Index Suppose that we have a table describing test outcomes. We wish to ensure that there is only one “success- ful” entry for a given subject and target combination for insertion will either insert or update. Unless there are unrelated errors, one of those two outcomes is guaranteed. If a conflict originates in another transaction whose effects are not yet visible

several principles in mind: • Implicit conversions should never have surprising or unpredictable outcomes. • There should be no extra overhead in the parser or executor if a query does not need implicit Example 11.3. Setting up a Partial Unique Index Suppose that we have a table describing test outcomes. We wish to ensure that there is only one “success- ful” entry for a given subject and target combination for insertion will either insert or update. Unless there are unrelated errors, one of those two outcomes is guaranteed. If a conflict originates in another transaction whose effects are not yet visible