nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DD fundamentals

curiousmaverick

A conceptual question here:

Datadeployment is done for the first time. In dd-config file, for one field attribute is set as null. few records are inserted. After that attribute for that filed is set as not null. Now will that change the constraint in the database table?

Find more posts tagged with

Comments

Rick Poulin

You seem to be talking about two different things.

DD can be configured to create your table if it does not exist. It has nothing to do with the content you deploy. I'm not sure it can automatically update table specifications without messing up your data, because some things like changing a nullable column to a non-nullable without setting a default value obviously poses some data consistency issues.

When you're deploying data on the other hand, if you deployed a null value into a nullable column the first time, and later deploy the record again with a value, then DD just updates the table rows (either via delete+insert or update, depending on your config). The content that you deploy will never have anything to do with modifying your DB schema.

Migrateduser

A conceptual question here:

Datadeployment is done for the first time. In dd-config file, for one field attribute is set as null. few records are inserted. After that attribute for that filed is set as not null. Now will that change the constraint in the database table?

if you change the setting in the DD config file, it does not alter the table, in fact, DD never does an alter on a table structure or contraints..

and I honestly never let DD create my tables..