Ref #1101 we've concluded to remove the MyGet feed, which has been used for pre-releases up until now. That involves several tasks. From the top of my head:

• Move all NuGet packages currently on the MyGet feed over to the Azure Artifacts feed
• Update readme.md to show a badge for the latest release on the new feed and remove MyGet
• Delete the Travis build script all together, or

A small issue, not sure if it happens on other versions of OS X, but the button to save the migrations to files is obscured by something or has a height of 1px. Here's a screenshot of it (the white line below the generated code):

The button is still click

I encountered a strange bug: I had a space in front of -- migrate:down, and the migration was getting applied, successfully, except that it wasn't being run (silently failing).

This was pretty bad and took a while for me to fix.

We should likely have stricter parsing of the syntax, if this can silently fail

Currently, the README.md file lists all tables with their full table comment.

I'm putting a lot of info in some of my table descriptions, including SQL code blocks. These render rather badly in the comment column of the central Tables table, which treats markdown just a little different.

Perhaps the Tables table should only use the first paragraph of each table description.

E.g.

getting started says:

run gnorm init to get a default gnorm.toml file and template files in the current directory. You need to at least set the ConnStr, DBType, and Schemas values... Now, to test your configuration, run gnorm preview. This will query your database and spit out all the information Gnorm knows about your database, including sche

A client defined a schema as CUBE and REF.

In schemacrawler, this comes back as "CUBE" or "REF", which our code isn't handling (note
SchemaCrawler.java:426 and SchemaRetriever:181)

If there are pending migrations for the database, setting the immediateDeploy flag to try should approve all pending migrations

How can I fix this?

$ ./vendor/bin/phpunit
PHPUnit 5.7.23 by Sebastian Bergmann and contributors.

EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE.F.EEEEEEEEEEEEEEEEE 65 / 97 ( 67%)
EEEEEEEEEEEEEEEEEEEEEEEEEE......                                  97 / 97 (100%)

Time: 422 ms, Memory: 8.00MB

There were 88 errors:

Postgres allows renaming indexes, and while it is impossible to use inside the schema diffing algorithm (as indexes are compared by name) it can still be used inside conditional migrations.

Adding an Operations::RenameIndex (and respective rename_index in the Migrator) and handling it with `execute('ALTER INDEX name RENAME TO new_

If you look in the README you will see that the screencast that we created for SchemaAnalyst has now been archived. I suggest that, at least for the short term, we delete this reference from the README. In the future, we might explore creating an animated GIF and then referencing that instead.