Support for NDB Cluster Engine

[trefster]

Does anyone know of a way to configure dotConnect to use the NDB Engine?

I'm using it in Entity CodeFirst, but it always creates INNODB tables. We really need support for clustering.

Thanks!

[Shalex]

Does anyone know of a way to configure dotConnect to use the NDB Engine?

Currently there is a possibility of setting the following engines in Code-First Migrations (via the CreateTableConfiguration anonymous argument in CreateTable):
* InnoDB,
* MyISAM,
* Memory,
* CSV,
* Archive

We are planning to add the NDB engine support. Also there will be a global option to use a particular engine for all tables in Code-First and Code-First Migrations. We will notify you when the feature is implemented.

[Shalex]

• The config.DatabaseScript.Table.StorageEngine option for possibility of setting MySQL storage engine for creating tables with CreateDatabase() and Code-First Migrations functionality is implemented
• The NDB storage engine is added to the list of available MySQL storage engines for Code-First

We will post here when the corresponding build of dotConnect for MySQL is available for download.

[jonathan82]

Hi, has this issue been resolved? How can I use Entity Framework Code first migrations with ndbcluster engine when creating a table?

[Shalex]

has this issue been resolved?

The functionality is available starting from the 7.6.242 (16-May-13) build: https://www.devart.com/dotconnect/mysql ... story.html.

How can I use Entity Framework Code first migrations with ndbcluster engine when creating a table?

Please set the engine in Code-First Migrations via the CreateTableConfiguration anonymous argument in CreateTable:

Code: Select all

  CreateTable("Blogs",
    c => new {
      BlogId = c.Int(nullable: false, identity: true),
      Name = c.String(unicode: false),
    },
    anonymousArguments: new CreateTableConfiguration() {
      StorageEngine = Devart.Data.MySql.Entity.MySqlStorageEngine.NDB
    }
  )
  .PrimaryKey(t => t.BlogId);