Schema Manager

[billy1624]

PR Info

• Resolve Schema Manager #12
• Required by Migration sea-orm#335
• Depends on
  • Add TableRef::DatabaseSchemaTable sea-query#193
  • Write database & schema prefix in TableRef for all databases sea-query#202

[billy1624]

I ignored the schema iden in TableRef::SchemaTable for MySQL, so the FROM below will now generate tables instead of information_schema.tables. It cause this error.

sea-schema/src/mysql/query/table.rs

Lines 52 to 81 in 16194d1

	pub fn query_tables(&self, schema: SeaRc<dyn Iden>) -> SelectStatement {
	type Schema = InformationSchema;
	Query::select()
	.columns(vec![
	TablesFields::TableName,
	TablesFields::Engine,
	TablesFields::AutoIncrement,
	TablesFields::TableCollation,
	TablesFields::TableComment,
	TablesFields::CreateOptions,
	])
	.column((
	Schema::CollationCharacterSet,
	CharacterSetFields::CharacterSetName,
	))
	.from((Schema::Schema, Schema::Tables))
	.left_join(
	(Schema::Schema, Schema::CollationCharacterSet),
	Expr::tbl(
	Schema::CollationCharacterSet,
	CharacterSetFields::CollationName,
	)
	.equals(Schema::Tables, TablesFields::TableCollation),
	)
	.and_where(Expr::col(TablesFields::TableSchema).eq(schema.to_string()))
	.and_where(Expr::col(TablesFields::TableType).eq(TableType::BaseTable.to_string()))
	.order_by(TablesFields::TableName, Order::Asc)
	.take()
	}
	}

[tyt2y3]

ooops. it does not seem to work :(

[billy1624]

ooops. it does not seem to work :(

PgInterval get renamed

[billy1624]

Try cherrypick 0929661

[tyt2y3]

okay so it's completely broken now

[tyt2y3]

I think we got a very problematic dependency tree here. As a rule-of-thumb, sea-schema should not directly depends on sea-orm. We might want to split out migration as a crate.

[tyt2y3]

Okay so the culprit is that sea-orm and sea-schema each has a dependency on sea-query, currently stuck in a deadlock, and there is no way to upgrade one side without breaking the other side.

We definitely have to re-architect this before releasing. The problem is the API exposed sea-query symbols and that tied things together. Ideally, sea-schema should be able to use a different sea-query version internally from sea-orm without causing trouble.

The migrator should use the sea-query pubed by sea-orm, or ideally, not using the high level sea-query interface at all.

[tyt2y3]

Merge to master for now. Note that sea-query is still stuck at 0.20, and we definitely want to upgrade to 0.21.