Skip to content

Provider-specific date/time types (e.g. NpgsqlDate) not supported in 2.1.0 #467

Open

Description

@iflight

After update to net core 2.1 and Npgsql.EntityFrameworkCore.PostgreSQL 2.1, EF throw exception:

System.InvalidOperationException: "The property 'TBReestr.TBrDateEnd' is of type 'Nullable<NpgsqlDate>' which is not supported by current database provider.

And same problem with Nullable<NpgsqlDateTime>.

part of Model:

    public class TBReestr
    {
        public long TBrId { get; set; }
        public NpgsqlDate? TBrDateStart { get; set; }
        public NpgsqlDate? TBrDateEnd { get; set; }
 }

modelBuilder:

     modelBuilder.Entity<TBReestr>(entity =>
            {
                entity.HasKey(e => e.TBrId);

                entity.ToTable("tBReestr");

                entity.Property(e => e.TBrDateStart)
                    .HasColumnName("tBR_DateStart");

                entity.Property(e => e.TBrDateEnd)
                    .HasColumnName("tBR_DateEnd");
}

Connection:

services.AddEntityFrameworkNpgsql().AddDbContextPool<DataContext>(options => options.UseNpgsql(configuration.GetConnectionString("DataConnection")));

Npgsql version: 4.0
Npgsql.EntityFrameworkCore.PostgreSQL 2.1
net core 2.1
PostgreSQL version: 9.6.6
Operating system: Win10

Activity

  1. self-assigned this
    on Jun 13, 2018
  2. iflight commented on Jun 13, 2018

    @iflight
    Author

    Why I use NpgsqlDate\NpgsqlDateTime instead of DateTime? We use (+-)Infinity values of timestamp in postgres base (Default values for some data in db). DateTime doesn't support it (maybe infinity must be mapped to DateTime.Max/.Min values, now i convert it in code).
    Migrate to NodaTime not easy when you has a lot of code with manipulating DateTime.
    p.s. Sorry for my English :(

  3. added this to the 2.1.1 milestone on Jun 13, 2018
  4. roji commented on Jun 13, 2018

    @roji
    Member

    You can specify Convert Infinity DateTime=true to access infinity values as DateTime.{Max,Min}Value, this allows you to avoid using the Npgsql-interactive specific types which are frankly not that great.

  5. changed the title [-]Nullable<NpgsqlDate> not supported by current database provider.[/-] [+]Provider-specific types (e.g. NpgsqlDate) not supported in 2.1.0[/+] on Jun 14, 2018
  6. modified the milestones: 2.1.1, Backlog on Jun 30, 2018
  7. roji commented on Jun 30, 2018

    @roji
    Member

    Moving to backlog as there's not much request for this, and we're considering deprecating the provider-specific date/time types altogether (npgsql/npgsql#2009).

  8. changed the title [-]Provider-specific types (e.g. NpgsqlDate) not supported in 2.1.0[/-] [+]Provider-specific date/time types (e.g. NpgsqlDate) not supported in 2.1.0[/+] on Dec 30, 2018
  9. added theissue type on Jun 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions