Fix incorrect behavior when adding an autoincrement column to a Postg…

[lilyrrose]

PR Info

Bug Fixes

Using the PostgresQueryBuilder I would've expected this:

Table::alter()
	.table(Test::Table)
	.add_column(
		ColumnDef::new(Test::Id)
			.integer()
			.auto_increment()
			.primary_key(),
	)

to give me: (This behavior is true if you use Table::create)
ALTER TABLE "test" ADD COLUMN "id" serial PRIMARY KEY

Instead it gave me:
ALTER TABLE "test" ADD COLUMN "id" integer PRIMARY KEY

Breaking Changes

If someone was using auto_increment() on anything but an integer, smallinteger, or biginteger it would cause a panic.

Changes

Modified the postgres alter_10 test to test against the correct behavior.

[lilyrrose]

of course I had to forget rustfmt, sorry ^^

[tyt2y3]

Thank you for your contribution

[github-actions]

🎉 Released In 0.30.2 🎉

Thank you everyone for the contribution!
This feature is now available in the latest release. Now is a good time to upgrade!
Your participation is what makes us unique; your adoption is what drives us forward.
You can support SeaQL 🌊 by starring our repos, sharing our libraries and becoming a sponsor ⭐.

[github-actions]

🎉 Released In 0.30.2 🎉

Thank you everyone for the contribution!
This feature is now available in the latest release. Now is a good time to upgrade!
Your participation is what makes us unique; your adoption is what drives us forward.
You can support SeaQL 🌊 by starring our repos, sharing our libraries and becoming a sponsor ⭐.