c# - Connection String Trouble MetaDataException -


In my project, I will get two models when I added other models, I found this error in all the account pages: 

  System.Data.MetadataException: The specified schema is not valid. Errors: (8.6): Error 0040: nclob type is not eligible with namespace or nickname Only the primitive type can be used without qualification lign 33: {lign 34: if (! Context.Database.Exists ()) lign 35: In line 34 of the 'Early Simili Ambership Entity CCT' using the {lign 36: // Make Simple Mailbish} Entity Framework Migration Schema   
 Without Database and those My Connection String:  
  & lt; connectionStrings & gt; & Lt; Add name = "DefaultConnection" connectionString = "user id = devart; password = 1234; data source = localhost: 1521" provider name = "devarart.data oracle" /> & Lt; Add name = "body" connection string = "metadata = ridge: //*/Models.ModelMAE.csdl | res: //*/Models.ModelMAE.ssdl | res: //*/Models.ModelMAE.msl; provider = Oracle.DataAccess.Client; Provider Connection String = & amp; quot; Data Source = Local Host: 1521; Password = 1234; USER ID = Test & amp; quot; "Provider Name =" System.Data.EntityClient "/> & Lt; / ConnectionStrings & gt;    
  usercontext  connection string 1:  
  public class UsersContext: DbContext {public UsersContext (): base ("DefaultConnection ") {} Public DbSet & lt; UserProfile & gt; UserProfiles {Receive; Set; }}  connectionString 2:  
  public class EntitiesMAE: DbContext {public entitiesMAE (): base ("name = EntitiesMAE ") {} Public DbSet & lt; OFFRE & gt; OFFRE {Received; Set; } Public DBSet & lt; Region & gt; Area {get; Set; }}   
 The problem is in the second second connection string  entities  when I delete it from everything please how to fix it?   
 
 
 It seems that it is related to this problem:  
  
 This article recommends two approaches 1. Disable the applications (I can not recommend it) 2. Use OracleEntityProviderConfig to configure the program. IgnoreSchemaName = true  
 They also mentioned using a specific DbContext template, which you can find from this article (I hate posting link, but in short there is a lot of information):  
  
 However, it was written for EF 4.1, and you do not say that you are using the version of EF ... so I'm not sure That if you can apply to any of these versions as well.  
 So the essence is that you can not just change the provider with other changes. You are going to make some other changes, and I recommend using code using the Devat DbContext template to generate the code. And see how it creates, then insert that app into your app.  
 In addition, the code is clearly incorrect. You are using connection strings that are not present (you say that the connection string is called entities, but your code is a connection string called antsaeme ), You can also say that your second reference is called user content, but your code is antitaimmace. I suggest clearing your code so that it is your real code, because otherwise we are trying to help you with code that is not valid.

Comments

Post a Comment

Popular posts from this blog

Java - Error: no suitable method found for add(int, java.lang.String) -

I'm in the middle of homework work and I'm stuck. At this point in my code, I think that I should have a GUI window that opens and allows me to type "inserted text number". Notice is not going anywhere but at this point, If I pass through the problem then it will be in a linked list. I am getting two of the same error for the lines. Add (index, element); And I can not seem to get past it, there is no suitable method for the error "add (int, java. string string)". Code is below, please advise. To clarify - this will not be a method error because it is a linked list. There should not be any way involved. import java.awt. *; Import java.awt.event. *; Import javax.swing. *; Import java.util. *; Import java.util.Scanner; Import java.util.LinkedList; Public class TopTenList JFrame {Private TopTenList tt; See the Private JTextArea list; Private JTextField cmdTextField; Private JTextField resultsTestfield; // This GUI window is the code for the public toptist...
Read more

java - JPA TypedQuery: Parameter value element did not match expected type -

I am using JPA 2.0 and getting the following code in the DAO layer: Public Zero Test () {string key = "status"; String [] Conditions = {"A", "B"}; & Lt; TestTable & gt; Results = Search (Keys, Conditions); } Public listing & lt; TestTable & gt; Search (string key, object value error) {string sql = "test ndf to testlet and jade nand." + Key + "in:" + key; TypedQuery & LT; TestTable & gt; Query = entityManager.createQuery (SQL, TestTable.class); Query.setParameter (key, Arrays.asList (valueArr)) / *** Error Line *** Return query.getResultList (); } In the above error line, it throws the following exception: java.lang.IllegalArgumentException: parameter value element [[Ljava.lang.String; @ cbe5bc] did not match the expected type [java.lang.String] Why is this expected type string while actually this string []? Please help! Note: This is derived from the normal routine and is a simplified code. I can no...
Read more

c++ - static template member variable has internal linkage but is not defined -

Yes, I know, there is a question with almost the same title, but it refers to a different situation. Error message) In my case, I have a .cpp file with a big named designation name (implementation details). There is a property class template with a static data member in that name space, which I need to access from outside the unknown namespace. I give it a little bit of meat: file.hpp namespace Bar {template & lt; Typename A & gt; Struct foo {static_assert (is_same & lt; a, float & gt; :: value} is_same & lt; a, double>: value, ""); Fixed zero set_static_var (a const & x); // ...}; } and file.cpp namespace {template & lt; Typename A & gt; Struct foo_traits {// supports the implementation of several static code bars: foo & lt; & Gt; Fixed A data; }; The template's & lt; & Gt; Float foo_traits & lt; Float & gt; :: datum; // No change if this is in the global namespace template & lt; & Gt; Doub...
Read more