Brar Piening

> I looked at this again with fresh eyes, and here's a bit of high-level thinking that you may not entirely like 😬 Well, if you make it appear like...

> I'm just a bit frustrated that we had a design discussion about how to go about this, and it didn't occur to me to make these comments back then....

> more with the inner loop when working inside the IDE Yeah, that's the second kind of problem I mentioned, which - as I understand the problems leading to the...

In case you or others use this together with generated/auto-incrementing columns, you may want to add `RESTART IDENTITY` to your `TRUNCATE` command. It shouldn't hurt and it avoids overflow of...

> I don't love this.. Specifically the fact that PostgresException inherits the Code property (since it extends NpgsqlException), so people will likely think that's the interesting property; but it isn't...

> getting Hint: To call a procedure, use CALL. See https://github.com/npgsql/npgsql/issues/2081#issuecomment-502632691

Since that one got punted for many milestones already I'm going to have a look at it. Be it only to trigger your rejections and hopefully better solutions.

> Yes it is returned true for ::1. Using long format is returned false. Interesting. > I am using net framework 4.7.2 (if relevant) Yes, that might be relevant. Maybe...

> I'm not too keen on copying System.IO.Path.IsPathRooted() just for the sake of supporting ::1 for .NET Framework I wouldn't want to re-introduce a build target for .NET framework but...

I'll have a look at this in the next few weeks.