Jochen van Wylick
Jochen van Wylick

Reputation: 5401

Invalid object name 'dbo.TableName' when retrieving data from generated table

I'm using entity framework code first to create my tables. Please note - create the tables, not the DB, since I'm working on a hosted environment and I don't have a user that is allowed to create db's.

Committing a DB update works fine, but retrieving data gives the exception:

Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'dbo.EventHosts'.

I've read that it happens because I'm not using EF Code First to create the DB. That's fine, but how do I elegantly solve this?

All the generated tables do not have a prefix like dbo. A solution like this doesn't work, and isn't elegant at all:

[Table("EventHosts", Schema = "")]

Upvotes: 4

Views: 27548

Answers (5)

Arsen Khachaturyan
Arsen Khachaturyan

Reputation: 8340

Ok, for me issue was that I had a table called dbo.UserState and in C# EF was trying to access dbo.UserStates because of pluralization.

The solution was to put Table attribute above class and specify the exact table name:

[Table("UserState")]
public class UserState
{
    [Key]
    public int UserId { get; set; }
}

Upvotes: 6

mrTurkay
mrTurkay

Reputation: 642

https://stackoverflow.com/a/12808316/3069271

I had same issue, it was pluralize problem between mapping and db.

Upvotes: 0

AishwaryaKasi
AishwaryaKasi

Reputation: 83

On of the reason for this error is the table named "EventHosts" may not Exist or that table is renamed to some other name please check with that..

Upvotes: 0

Ladislav Mrnka
Ladislav Mrnka

Reputation: 364389

To answer your first question: use the schema created for you by your hosting provider.

To answer your second question: No there is currently no direct way to change the default schema globally because you cannot modify existing conventions or create new conventions. You can try to hack it.

For example you can override OnModelCreating and use reflection to get all DbSet<> properties declared in your context. Than you can just use simple loop on these properties and create ToTable mapping call with name of the property as table name and your custom schema. It will require some playing with reflection to make this work.

Alternatively you can try to do some reusable approach by implementing custom conventions. You can find many different articles about using your own conventions with EF. Some examples:

My high level untested idea is following same principle and create assembly level attribute which will be processed by the convention mechanism and applied on all your entities.

Upvotes: 2

Eray Aydogdu
Eray Aydogdu

Reputation: 250

Try to set default schema name to 'dbo' in SQL SERVER.

http://msdn.microsoft.com/en-us/library/ms173423.aspx

Upvotes: 0

Related Questions