Replies: 1 comment 1 reply
-
@fubar-coder I was just bit by writing
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
AsDecimal(const x, const y)
validates x precision is not > 28 (reason: .NET does not allow decimal values greater than 28 digits).Alter.Table("Foo").InSchema("dbo").AddColumn("x").AsDecimal()
NotNullable
Alter.Table("Foo").InSchema("dbo").AddColumn("x").AsDateTime();
AsDateTime2
instead, as it is ANSI DateTime.AsDateTime
withAsDateTime2
.Alter.Table("Foo").InSchema("dbo").AddColumn("x").AsDateTime2();
Alter.Table("foo").InSchema("dbo").AddColumn("x").AsDecimal().NotNullable();
should warn that you need to useSetExistingRowsTo
to avoid run-time errors where the column is not seeded. See discussion in Update column where value is not null #1379 - it doesn't need to beAsDecimal
and can be for any data type.Delete.FromTable("Foo").InSchema("dbo");
.Row();
or.AllRows();
.Row();
.AllRows();
TransactionBehavior.None
. Ex: Add support for concurrently and only index #1385 Postgres Concurrently[Migration(int, string, TransactionBehavior.Default]
[Migration(int, string, TransactionBehavior.None]
[Migration(int, string)]
[Migration(int, string, TransactionBehavior.None]
string TransactionBehaviorJustification
overload to the MigrationAttribute constructor? Common justifications might be "knowable" by the analyzer, so that if you remove Concurrently, it realizes the justification is no longer valid? Too fancy/complex?[Tags("SomeTag")]
attribute but no[Migration(0)]
attributeBeta Was this translation helpful? Give feedback.
All reactions