Samuel Colvin

Looks good to me, thanks.

For anyone else who comes to this issue [here](https://github.com/samuelcolvin/watchfiles/blob/6636d3d20c53677b2d8cde7ab269e3a3086609b2/src/lib.rs#L153-L182) is the logic in watchfiles which catches this error and falls back to the poll watcher. In particular, we catch this...

Taken from #405, as that was marked as a duplicate: > Thanks so much for notify, it's great and I've had a really great experience wrapping it for the [watchfiles](https://github.com/samuelcolvin/watchfiles)...

Thanks so much @pksunkara, this resolves my immediate problem.

FWIW, there's pretty complete denounce logic in watchfiles (implemented in rust), see [here](https://github.com/samuelcolvin/watchfiles/blob/acea996e0081cfa323056c6195729b6a749c41c5/src/lib.rs#L172-L228). Feel free to use any of it.

Will do, please let us when it's released.

Heres the diff for anyone else who finds it helpful: https://github.com/notify-rs/notify/compare/5.0.0-pre.15...5.0.0-pre.16 Changes I encountered: * `PollWatcher::with_config` has become `PollWatcher::new` * `RecommendedWatcher::new`'s signature has changed to take a `config` argument. *...

I think the intermittency was because either: the table didn't have a sequence on the primary key (different table from above) or there was only one value in `values` the...

Ok, this issue is related to the explicit use of `Sequence('subject_id_seq')` removing that (and thereby using the default `SERIAL` as per [this](http://docs.sqlalchemy.org/en/latest/dialects/postgresql.html)) seems to solve the problem. Still an error...

this is great, thanks so much.