When determining if a schema change occurred, one of the tables Prisma looks at is the information_schema.columns.
Here, we incorrectly mark all datetime and timestamp columns as with a precision of 6.
If a table has type DATETIME(3), Prisma would think there was a schema change, and perform a migration when one isn't needed.
This PR addresses this issue by having the information_schema.columns table accurately reflect the datetime preicision of the columns,
When determining if a schema change occurred, one of the tables Prisma looks at is the
information_schema.columns. Here, we incorrectly mark alldatetimeandtimestampcolumns as with a precision of 6. If a table has typeDATETIME(3), Prisma would think there was a schema change, and perform a migration when one isn't needed.This PR addresses this issue by having the
information_schema.columnstable accurately reflect the datetime preicision of the columns,fixes: https://github.com/dolthub/dolt/issues/8173