Eli Ribble
393836a86a
This is kind of a wild one. Turns out that the triggers I was using actually fire before the transaction is closed and I was primarily getting lucky that the job was present on the other side of the connection rather than having things built correctly. I've fixed this by removing the trigger entirely and instead manually triggering as part of the transaction. This makes the NOTIFY call happen as soon as the transaction closes, just at the cost of making my application be in charge of ensuring the NOTIFY gets called. Seems like a win. Part of doing this is porting the existing job creation code over to use Jet. It's something I want to do anyway, so it's a win all around.
18 lines
440 B
SQL
18 lines
440 B
SQL
-- +goose Up
|
|
CREATE TYPE fileupload.PoolCondition AS ENUM (
|
|
'blue',
|
|
'dry',
|
|
'false pool',
|
|
'unknown',
|
|
'green',
|
|
'murky'
|
|
);
|
|
ALTER TABLE fileupload.pool
|
|
ALTER COLUMN condition TYPE fileupload.poolcondition
|
|
USING condition::text::fileupload.poolcondition;
|
|
|
|
-- +goose Down
|
|
ALTER TABLE fileupload.pool
|
|
ALTER COLUMN condition TYPE public.poolconditiontype
|
|
USING condition::text::poolconditiontype;
|
|
DROP TYPE fileupload.PoolCondition;
|