Devart Forums

Well, ok, but i've been trying to load mapping from file for over a month now. And i think this is a much more critical issue than e.g. support for multiple diagrams per model in Entity Developer...

Using the latest version, i still get a XmlSchemaException : Guid

at Devart.Data.Linq.Mapping.aj.b(XmlReader A_0, String[] A_1)
at Devart.Data.Linq.Mapping.aj.g(XmlReader A_0)
at Devart.Data.Linq.Mapping.XmlMappingSource.FromReader(XmlReader reader)
at Devart.Data.Linq.Mapping.XmlMappingSource.FromStream(Stream stream)

If i remove all the Guid attributes (what is this exactly? I opened an older lqml with the latest Entity Developer and when i saved, every entity & column had a Guid attribute...), i get a same MaxLength exception. Gosh...

Well, this is an Enum type and the implementation should take into account the final Enum support you plan to integrate into the product. The string server data type is ok for me, particularly if you honor the Fixed Length & Max Length facets, for me an Enum in Oracle is a Char(1) or varchar2(2) data types. But for others, it can be something else, an int maybe. So, there is more to it than a simple fallback scenario which is ok with a really unknown data type.

I have already created a relevant support ticket titled "Error when trying to generate Database through Entity Developer." since 17/01 where the relevant info along with the problematic lqml file are presented.

Yes, the aforementioned check is disabled. So, i enable it and enter proper DBMS Type and schema and close. A Database Connection is created in the Database Explorer which does not have proper connection string. What is the point of that? Maybe a better design should be applied...

Nevertheless, i enter the correct connection string. I go to the Generate Database option where i enable the Regenerate Storage option and proceed until i get an exception, i guess at the final step:

Exception Information
=========================
Message: convertType
Source: EntityDeveloper.Common
TargetSite: Void AddMainDefinition(System.String, EntityDeveloper.ServerDataTypeInfo, Boolean, System.Text.StringBuilder)
HelpLink:
Type: System.ArgumentException
Stack:
at EntityDeveloper.OracleDataTypeGenerator.AddMainDefinition(String dataTypeName, ServerDataTypeInfo typeInfo, Boolean isIncludeDimensions, StringBuilder sb)
at EntityDeveloper.BaseDataTypeGenerator.GetServerTypeName(String dataTypeName, ServerDataTypeInfo typeInfo, ServerDataTypeGenerationBehaviour behaviour)
at EntityDeveloper.Linq.LinqModelMapper.a(LinqProperty A_0)
at EntityDeveloper.Linq.LinqModelMapper.b(LinqProperty A_0, String A_1)
at EntityDeveloper.Linq.LinqModelMapper.AddPropertyMapping(Property property)
at EntityDeveloper.ModelMapper.AddModelMapping()
at EntityDeveloper.ai.b()
at EntityDeveloper.ai.d(Boolean A_0)
at EntityDeveloper.c7.l(Boolean A_0)
at EntityDeveloper.co.u()
at EntityDeveloper.fc.b(Object A_0, EventArgs A_1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)

Ok, how does that affect Batch Updates? do i still need to change the Update Check to Never even for the primary keys?

1). I do not have ANY server data types or source properties defined in my model because i removed them. The reason was, that i need to create a schema with the more strict .NET types defined in my model.

Hello,

You mention in your help file, that in order for an update to participate in a batch update, all properties should be marked as UpdateCheck = Never. Does this also apply to the Primary Key property? In fact, what is the purpose of this attribute on a Primary Key column? I guess all updates are performed checking that the primary key property has not changed its value...

I forgot to disable the Just My Code parameter.

I get 2 System.NotSupportedException exceptions : Keyword not supported: 'sid', 'direct'
at Devart.Data.Oracle.OracleConnectionStringBuilder.a(String A_0)

I removed the entries from the Connection String and the model opened.

Nevertheless, i didn't put those entries in there my hand! How come Entity Developer do not recognize them? I guess the problem was that i created the first version of lqml file many versions ago and when i recently tried to reopen it, backward compatibility had a problrm to work properly.

And the thing that you say, that you can open the file without any problem!!!

Hello,

I need to migrate a database schema, along with the relevant data context model, from Oracle to SQL Server. So, i used the Database First approach and created the model from my Oracle Database. I made a lot of changes on the generated data types etc.

Now, i need 2 things:

1). Create an Oracle generation script, without taking into account the Server Data Types of my properties. I need to do this, because the correct data types are changed and properly defined in Type and Facets properties. e.g for all the numbers, my database had a NUMBER data type. I need to change it to more specific numeric data types as defined in my model.

2)> Create an SQL Server generation script as above. If i change the type of Database Connection, Entity Developer still takes the old Server Data Types into account and the generated script is invalid because it still uses the Oracle data types.

Is there a proper way to do this? Or maybe if i just manually remove all the DbType attributes from the lqml file, i will effectively changed my model as if i created it using the Model First approach?

Ok, you can discard the LEVEL column for now. In any case, the hierarchy can be reconstructed out of the list of entities, by checking the self-referencing column value. It is a simple recursion algorithm.

So, it would be nice if you can support the aforementioned type of queries.

Done all of the above, and the lqml still does not open. I attached Visual Studio and no exceptions are thrown...

Same behavior encountered in other 3 workstations. No developer can open the file...

LinqConnect version 2.00.10.

Purpose for the use of such queries is efficiency and performance. Instead of making recurrent queries in each level of a hierarchy, a single query can return the requested data.

Examples of use are:
1). Get the entities of the hierarchy in which a specific entity belongs. Get only the ascendants or only the descendants or the full hierarchy.

2). Get the root entity of the hierarchy in which a specific entity belongs.

In almost all the queries, the returned result can be the whole entity or list of entities or a subset of the properties.

The use of the Level of an entity in a hierarchy is paramount to all these queries. The Level should be available in projection methods as well as in ordering the result set according to it.

It is apparent, that the LINQ approach offers the extra value of DB-agnostic implementation. I need to be able to attach my solution to a SQL Server as well as to an Oracle database. For now, my code is polluted with hundreds of non-LINQ, pure SQL string based hierarchical queries surrounded by the required switches based on the type of connected DB.

As you can see, this is way far from the relevant features on which you base the advertisement of the LinqConnect product...

I recently switched from dotConnect for Oracle to LinqConnect and it seems that my lqml file is messed up. Using the latest version of Entity Developer 3.0.60, my lqml file does not open and no errors are reported. Using version 3.0.50, it opens. I will send you my lqml file through the support page and i would be obliged if you could fix it.

Maybe you can find the problem with the file mapping.

Anything new on that?