The ORM Foundation

Get the facts!

The specified invariant name is not supported

Last post 01-20-2014 10:37 by josecarlus. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 12-18-2007 9:10

    The specified invariant name is not supported

    I want to reengineer an existing database-schema using ORM. 
    I used Import DB (File->New Item->Object-Role Modeling (DB Import).
    After specifying and testing the connection I get the following error message: 
    The specified invariant name is not supported.
    Is there a solution to solve this? 
    I tried different data sources and connections are working.
    I’m using Neumont ORM Architect for Visual Studio 2007-11CTP.
  • 01-24-2008 19:02 In reply to

    RE: The specified invariant name is not supported

    Jeez, lousy error message. Sorry.
    We currently support two DataProvider names:
    Other connection types are not currently supported.
    Please feel free to code providers for other connection types:) The Tools\DatabaseImport project is the place to add them, with the provide mappings in the DcilObjectModel.cs file (GetDcilSchemaProvider method). Obviously, we would like to extend the set of support targets.
    A couple of known limitations:
    1) Spaces in the DB schema/table/column names end up as spaces in intermediate XML file identifier attributes, which is not allowed. We'll fix this one.
    2) Import from more than one SQL owner is not currently supported. The is significant work to be done in this area to support this across the board.
    You will also see better ORM coming in from the export as time goes on. We added basic join tables in December, more pattern recognition will follow (but probably not this quarter).
  • 01-13-2014 16:28 In reply to

    Re: RE: The specified invariant name is not supported

    Hi Matt,

    I get this message with Oracle (ODP.NET). By the way, did you add support for any other data provider?


  • 01-16-2014 18:04 In reply to

    Re: RE: The specified invariant name is not supported

    Sorry,  José, I haven't done any work in this area.

    This comes down to writing a file for Oracle that is similar to and plugging it into the GetDcilSchemaProvider method in DcilObjectModel.cs in the same directory.

    I actually started this process for Postgres last year, but I blew my development time just finding a provider that would hook up cleanly to VS and get me a viable DB connection. I didn't even get to the code.

    If you're using an Oracle system with VS, maybe you can give me some links to the bits I need to install to get there myself. I need to be able to open a Data Connection in the Server Explorer window as this uses the same facilities to connect as the database import. I'd also welcome any tips on the queries needed to extract the schema information from a db (I'm using the normal meaning of schema, not the weird Oracle user account meaning of the term).


    PS Free versions are good. I don't have the cash to drop on this for the privilege of writing code for a couple of days.

  • 01-20-2014 10:37 In reply to

    Re: RE: The specified invariant name is not supported

    Hi Matt,

    I worked on this during the weekend and I think I got a working version for Oracle. I tested it with these providers:

    - OracleClient from Microsoft (System.Data.OracleClient), and

    - ODP.NET from Oracle (Oracle.DataAccess.Client), this provider comes with the ODAC set of libraries developed by Oracle. I used the 32-bit version which you can download from this page:

    I made some tests and they all worked well, I could import an Oracle schema and generate the orm file. I am sending you this file along with the modified source files. I'm not sure if the data type mappings are 100% correct, I just tried some of them.

    This was my development configuration, just in case:

    - Windows 7, 64 bits.

    - Visual Studio 2010, professional ed.

    - ODAC 11.2 Release 4 (

    - Oracle database 9i 

    I think the code could work without modifications with ODP.NET as well. With version 12, maybe it's necessary to add a new name to reference the provider considering that the namespace has changed to something like Oracle.ManagedDataAccess.Client. 


Page 1 of 1 (5 items)
© 2008-2014 The ORM Foundation: A UK not-for-profit organisation -------------- Terms of Service