datalust / piggy Goto Github PK

Currently, only the default PostgreSQL server port is used; the connection feature should allow this to be overridden.

A quick glance through the docs doesn't mention rollbacks. Does piggy have support for a rollback command and associated "down" sql to specify rollback behavior (eg; as in https://github.com/thuss/standalone-migrations)?

A few possible additions:

• Some kind of "what-if" command to view the changes that would be applied by up
• A "rebase"-type command to handle reorganized scripts; e.g. clear the change log table and insert all scripts as "run" without executing them
• A "forget" command to remove a specific entry from the change log

I just noticed that after installing the new Datalust.Piggy package, some unexpected content is linked into my CSPROJ:

(We get the Piggy icon and Attribution folder.)

Guessing this is a side-effect of publishing the project as an executable before packaging it as a library :-)

PostgresException carries line and column numbers, but we're not surfacing these in failure messages. I'm unsure if/when they'll be set, but it seems like a good bet there will be useful information there.

Would be great if you could install and use piggy as a DotNetCliToolReference.

:) Looking good otherwise, going to test run this with our proj soon!

Relative script filenames should produce the same persisted script name on all platforms. Currently, path separators are replaced with / uniformly, but e.g. escaped spaces and escaped separators may cause script names to differ depending on the platform from which Piggy is run.