Adding DateTime2 parameter

[maxoizs]

Adding full DateTime with milliseconds in petepoco AddParam will be treated as DateTime which will loss the milliseconds part, and if I amend the if else case with

else if (item.GetType().Name == "DateTime")
        {
          p.DbType = DbType.DateTime2;
          p.Value = item;
        }

will treat all DateTime parameters as DateTime2 which ok in my case as I'm using DateTime2 everywhere but it'll invalid the where clause for DateTime parameter if it's against DateTime only column.

I wonder if it possible to determine the column type for the parameter ?

[pleb]

Seems like something that PP should allow to be configured

[0ndrej]

I just bumped into this problem now. Recommended type for MSSQL date is datetime2, while PetaPoco is mapping everything to datetime. If I create POCO class with .NET DateTime property, exception is thrown when trying to Insert, because of SQL datetime overflow even though it is defined as datetime2 in database.

[tkouba]

One possible solution is adding function to interface IProvider DbType MapParameterValue(object value, PropertyInfo pi); and use it in Database.AddParam. What is your opinion?

[maxoizs]

Sorry guys, It's been so long and I've actually forgot about it totally. therefore I'm sure I won't be of much help.

[pleb]

No worries mate. I should have some free time starting mid-year. Tickets, list this one, are on my list ;)

[roggmaeh]

I just have the same problem. Is a fix like AnsiString workaround (varchar/nvarchar) possible?

[roggmaeh]

AnsiString and DateTime2 fix
roggmaeh@7ef1a8f

my table model
[Column("DATECHANGE", IsDateTime2 = true)]
public DateTime? DATECHANGE {get;set;)

[Column("NAME", IsAnsi = true)]
public string NAME {get;set;}

[asherber]

@roggmaeh Can you please open a pull request so we can review and comment?

[asherber]

Please see my comments in the PR. I'm not sure that this work is needed.