Docs Menu
Docs Home
/
Relational Migrator
/
Projects

Configuring Project Settings

On this page

  • Open Project Settings Dialog
  • Configurable Project Settings

After you create a Relational Migrator project, you can configure settings for that project.

Note

To learn how to create a Relational Migrator project, see Creating a Project.

Open Project Settings Dialog

To open the Project Settings dialog:

  1. From the Relational Migrator home page, click the target project.

  2. From the project view, the gear icon next to your project's name.

Configurable Project Settings

You can configure the following settings for your project:

Key Handling Options

Specifies how the _id field is populated when new documents are inserted into a collection. You can choose one of the following options:

  • Autogenerated ObjectId

    • Your _id field is populated with an autogenerated random ObjectId.

      Autogenered ObjectId is the default key handling strategy used when creating a new project.

      You may choose to keep the original primary key as a different field in the collection.

      For example, if your relational table row has a primary key of personId = 1, after migration your MongoDB _id field is _id: ObjectId("62472f3d5849820a91d7b52f").

  • Single Inherited Primary Key

    • Your _id field is populated with the value of the primary key field. The name of your primary key field is not included in the _id.

      For example, if your relational table row has a primary key of personId=1, after migration your MongoDB _id field is _id: 1.

  • Wrapped Inherited Primary Key

    • Your _id field is populated with an object where the key is the name of your primary key field and the value is the value of your primary key field.

      For example, if your relational table row has a primary key of personId = 1, after migration your MongoDB _id``field is ``_id: { personId: 1 }.

Key Handling Behavior

  • If your relational table has more than one field in its primary key and you select the single strategy, collections receiving data from that table use the wrapped key handling strategy. The single strategy only works for tables that have a single primary key.

  • If your relational table does not have a primary key, collections receiving data from that table use the generated strategy even if you select a different global strategy.

Global Casing

You can choose one of the following options:

  • Keep Original: Keep the original casing used in your relational database table name.

  • Override with Global Casing: Override the original table name with a global casing convention.

    • camelCase

    • TitleCase

    • kebab-case

    • snake_case

    • UPPER_SNAKE_CASE

Note

Changing this setting after creating a project only impacts mappings created after the setting change. Mappings created prior to changing this setting are not affected.

Suggested Mappings

Enabling Suggested mappings allows Relational Migrator to automatically suggest mapping rules based upon your relational schema.

← Create a Project by Using a Sample Schema
Manage the Relational Model →

On this page