Blob issue with entity framework 5

I am getting this exception upon initial entity framework migration of my postgres db:

Error Exception: Npgsql.PostgresException (0x80004005): 42704: type "blob" does not exist
   at Npgsql.NpgsqlConnector.<ReadMessage>g__ReadMessageLong|194_0(NpgsqlConnector connector, Boolean async, DataRowLoadingMode dataRowLoadingMode, Boolean readingNotifications, Boolean isReadingPrependedMessage)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlDataReader.NextResult()
   at Npgsql.NpgsqlCommand.ExecuteReader(CommandBehavior behavior, Boolean async, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteReader(CommandBehavior behavior, Boolean async, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteNonQuery(Boolean async, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteNonQuery()

Here is my create script:

table.Column<byte[]>(maxLength: 16, nullable: false),
b.Property<byte[]>("BytesColumn")
      .IsRequired()
      .HasColumnType("BLOB")
      .HasMaxLength(16);

Is there nothing that changes blob to bytea?

Changing the “BLOB” entries to “bytea” does not fix the issue.

Using latest version of the nuget as os 2021-03-16.

[roji]

@jjxtra data types simply aren’t the same across database; it’s not just a question of blob vs. bytea - SQL Server has nvarchar whereas PostgreSQL has text. It doesn’t make any sense to make the PostgreSQL migrations provider recognize all data types of all other database…

Note also that there are various other differences between databases - not just data type names - which also affect migrations. So this approach wouldn’t work in the general case.

Please take a look at the docs I linked to above on managing migrations and multiple databases. You typically need to generate each migration for your different supported databases.

[jjxtra]

I am changing blob to bytea so that I don’t have to maintain a sqlite and postgres migration, as I mentioned earlier, every other sqlite datatype is compatible with postgres, so having this one line of code added would be nice, even if it’s not officially postgres standard. All my tests use sqlite, and production servers use postgres.