Error "column c.CreatedOn does not exist..." in PostgreSQL logs during code first context initialization using the Devart dotConnect provider

Question

I'm getting the following error in my PostgresSQL logs whenever my context is initialized:

2014-06-03 09:51:25 PDT ERROR:  column c.CreatedOn does not exist at character 10
2014-06-03 09:51:25 PDT STATEMENT:  SELECT 

    c."CreatedOn"

    FROM "__MigrationHistory" AS c

    LIMIT 1

Everything seems to work okay for the most part, but I'd like to better understand the error and make it go away if possible.

Is this an error with the dotConnect provider or am I expected to add this custom column to my __MigrationHistory table?

Devart · Accepted Answer · 2014-06-04 11:13:50Z

4

The "column c.CreatedOn does not exist" exception is expected for this scenario. This is the internal logic of Entity Framework.

The CreatedOn column is used only in EF 4.3 and below. However, the internal check for the table "__MigrationHistory" and, accordingly, for the "CreatedOn" column still exists and, consequently, in the later EF versions this gives an error. However, the implementation of this request does not stop the application and does not affect the result.

answered Jun 4, 2014 at 11:13

Devart

120k23 gold badges172 silver badges189 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Dr Rob Lang Over a year ago

You might start seeing this if you uncheck the option Tools -> Options -> Debugging -> General -> Enable Just My Code.

Collectives™ on Stack Overflow

Error "column c.CreatedOn does not exist..." in PostgreSQL logs during code first context initialization using the Devart dotConnect provider

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related