Object Relational Mapping
Creating Records
Reading Records
Updating Records
Deleting Records
Column Statistics
Dynamic Finders
Getting Paginated Data
Associations
Nested Properties
Object Validation
Object Callbacks
Calculated Properties
Transactions
Dirty Records
Soft Delete
Automatic Time Stamps
Using Multiple Data Sources
dbmigrate create column
Generate a migration file for adding columns to an existing database table.
Synopsis
wheels dbmigrate create column name=<table_name> dataType=<type> columnName=<column> [options]
Alias: wheels db create column
Description
The dbmigrate create column
command generates a migration file that adds a column to an existing database table. It supports standard column types and various options for column configuration.
Parameters
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| name
| string | Yes | - | The name of the database table to modify |
| dataType
| string | Yes | - | The column type to add |
| columnName
| string | Yes | - | The column name to add |
| default
| any | No | - | The default value to set for the column |
| --null
| boolean | No | true | Should the column allow nulls |
| limit
| number | No | - | The character limit of the column |
| precision
| number | No | - | The precision of the numeric column |
| scale
| number | No | - | The scale of the numeric column |
Column Types
string
- VARCHAR(255)text
- TEXT/CLOBinteger
- INTEGERbiginteger
- BIGINTfloat
- FLOATdecimal
- DECIMALboolean
- BOOLEAN/BITdate
- DATEtime
- TIMEdatetime
- DATETIME/TIMESTAMPtimestamp
- TIMESTAMPbinary
- BLOB/BINARY
Migration File Naming
The generated migration file will be named with a timestamp and description:
[timestamp]_create_column_[columnname]_in_[tablename]_table.cfc
Example:
20240125160000_create_column_email_in_user_table.cfc
Examples
Add a simple column
wheels dbmigrate create column name=user dataType=string columnName=email
Add column with default value
wheels dbmigrate create column name=user dataType=boolean columnName=is_active default=true
Add nullable column with limit
wheels dbmigrate create column name=user dataType=string columnName=bio --null=true limit=500
Add decimal column with precision
wheels dbmigrate create column name=product dataType=decimal columnName=price precision=10 scale=2
Generated Migration Example
For the command:
wheels dbmigrate create column name=user dataType=string columnName=phone --null=true
Generates:
component extends="wheels.migrator.Migration" hint="create column phone in user table" {
function up() {
transaction {
addColumn(table="user", columnType="string", columnName="phone", allowNull=true);
}
}
function down() {
transaction {
removeColumn(table="user", column="phone");
}
}
}
Use Cases
Adding User Preferences
Add preference column to user table:
# Create separate migrations for each column
wheels dbmigrate create column name=user dataType=boolean columnName=newsletter_subscribed default=true
wheels dbmigrate create column name=user dataType=string columnName=theme_preference default="light"
Adding Audit Fields
Add tracking column to any table:
wheels dbmigrate create column name=product dataType=integer columnName=last_modified_by --null=true
wheels dbmigrate create column name=product dataType=datetime columnName=last_modified_at --null=true
Adding Price Fields
Add decimal columns for pricing:
wheels dbmigrate create column name=product dataType=decimal columnName=price precision=10 scale=2 default=0
wheels dbmigrate create column name=product dataType=decimal columnName=cost precision=10 scale=2
Best Practices
1. Consider NULL Values
For existing tables with data, make new columns nullable or provide defaults:
# Good - nullable
wheels dbmigrate create column name=user dataType=text columnName=bio --null=true
# Good - with default
wheels dbmigrate create column name=user dataType=string columnName=status default="active"
# Bad - will fail if table has data (not nullable, no default)
wheels dbmigrate create column name=user dataType=string columnName=required_field --allowNull=false
2. Use Appropriate Types
Choose the right column type for your data:
# For short text
wheels dbmigrate create column name=user dataType=string columnName=username limit=50
# For long text
wheels dbmigrate create column name=post dataType=text columnName=content
# For money
wheels dbmigrate create column name=invoice dataType=decimal columnName=amount precision=10 scale=2
3. One Column Per Migration
This command creates one column at a time:
# Create separate migrations for related columns
wheels dbmigrate create column name=customer dataType=string columnName=address_line1
wheels dbmigrate create column name=customer dataType=string columnName=city
wheels dbmigrate create column name=customer dataType=string columnName=state limit=2
4. Plan Your Schema
Think through column requirements before creating:
- Data type and size
- Null constraints
- Default values
- Index requirements
Advanced Scenarios
Adding Foreign Keys
Add foreign key columns with appropriate types:
# Add foreign key column
wheels dbmigrate create column name=order dataType=integer columnName=customer_id
# Then create index in separate migration
wheels dbmigrate create blank name=add_order_customer_id_index
Complex Column Types
For special column types, use blank migrations:
# Create blank migration for custom column types
wheels dbmigrate create blank name=add_user_preferences_json
# Then manually add the column with custom SQL
Common Pitfalls
1. Non-Nullable Without Default
# This will fail if table has data
wheels dbmigrate create column name=user dataType=string columnName=required_field --allowNull=false
# Do this instead
wheels dbmigrate create column name=user dataType=string columnName=required_field default="pending"
2. Changing Column Types
This command adds columns, not modifies them:
# Wrong - trying to change existing column type
wheels dbmigrate create column name=user dataType=integer columnName=age
# Right - use blank migration for modifications
wheels dbmigrate create blank name=change_user_age_to_integer
Notes
- The migration includes automatic rollback with removeColumn()
- Column order in down() is reversed for proper rollback
- Always test migrations with data in development
- Consider the impact on existing queries and code
Related Commands
wheels dbmigrate create table
- Create new tableswheels dbmigrate create blank
- Create custom migrationswheels dbmigrate remove table
- Remove tableswheels dbmigrate up
- Run migrationswheels dbmigrate down
- Rollback migrations
- Synopsis
- Parameters
- Column Types
- Migration File Naming
- Examples
- Add a simple column
- Add column with default value
- Add nullable column with limit
- Add decimal column with precision
- Generated Migration Example
- Use Cases
- Adding User Preferences
- Adding Audit Fields
- Adding Price Fields
- Best Practices
- 1. Consider NULL Values
- 2. Use Appropriate Types
- 3. One Column Per Migration
- 4. Plan Your Schema
- Advanced Scenarios
- Adding Foreign Keys
- Complex Column Types
- Common Pitfalls
- 1. Non-Nullable Without Default
- 2. Changing Column Types
- Notes
- Related Commands