Frequently Asked Questions

Common questions about Crystal Query Language (CQL) and its Active Record implementation.

General CQL Questions

Q: What is CQL?

A: CQL is an Object-Relational Mapping (ORM) library for Crystal that provides type-safe database interactions through an Active Record pattern with support for PostgreSQL, MySQL, and SQLite.

Q: How do I install CQL?

A: Add CQL to your shard.yml:

dependencies:
  cql:
    github: azutoolkit/cql
    version: "~> 1.0"

Then run shards install. See the Installation Guide for details.

Q: Which databases does CQL support?

A: CQL supports PostgreSQL, MySQL, and SQLite through Crystal DB drivers.

Q: How does CQL compare to other ORMs?

A: CQL leverages Crystal's compile-time type safety, provides zero-cost abstractions through macros, and supports multiple design patterns (Active Record, Repository, Data Mapper).

Active Record Questions

Q: How do I define a model?

A: Create a Crystal struct with CQL::ActiveRecord::Model:

struct User
  include CQL::ActiveRecord::Model(Int64)
  db_context UserDB, :users

  property id : Int64?
  property name : String
  property email : String
end

See Defining Models for details.

Q: How do I perform CRUD operations?

A: Use built-in methods:

# Create
user = User.create!(name: "Alice", email: "[e-mail]")

# Read
user = User.find!(1)
users = User.where(active: true).all

# Update
user.update!(name: "Alice Smith")

# Delete
user.delete!

See CRUD Operations for more examples.

Q: How do I define relationships?

A: Use association macros:

struct User
  has_many :posts, Post
  has_one :profile, UserProfile
end

struct Post
  belongs_to :user, User
end

See Relations for all relationship types.

Q: How do validations work?

A: Define validations in your model:

struct User
  validate :name, presence: true, size: 2..100
  validate :email, presence: true, match: EMAIL_REGEX
end

See Validations for details.

Q: What are callbacks?

A: Callbacks run code at specific points in a model's lifecycle:

struct User
  before_save :normalize_email
  after_create :send_welcome_email

  private def normalize_email
    self.email = email.downcase.strip
  end
end

See Callbacks for more information.

Q: What's the difference between save and save!?

A: Methods with ! raise exceptions on failure, while methods without return false:

user.save   # Returns true/false
user.save!  # Returns true or raises CQL::RecordInvalid

user = User.find(1)    # Returns user or nil
user = User.find!(1)   # Returns user or raises CQL::RecordNotFound

Q: How do migrations work?

A: Define schema changes in migration classes:

class CreateUsers < CQL::Migration
  def up
    create_table :users do |t|
      t.string :name, null: false
      t.string :email, null: false
      t.timestamps

      t.index :email, unique: true
    end
  end

  def down
    drop_table :users
  end
end

See Migrations for details.

Q: Does CQL support transactions?

A: Yes, CQL provides transaction support:

User.transaction do
  user1.save!
  user2.save!
  # Both succeed or both rollback
end

See Transactions for more examples.

Troubleshooting

Q: How do I debug SQL queries?

A: Enable query logging in development:

MyDB = CQL::Schema.define(
  :mydb,
  adapter: adapter,
  uri: uri,
  log_level: :debug  # Shows generated SQL
)

Q: My queries are slow. How do I optimize them?

A: Common optimization strategies:

• Add appropriate indexes to frequently queried columns

• Use select to limit returned columns

• Use includes or joins to avoid N+1 queries

• Implement pagination for large result sets

See Performance Optimization for details.

Q: Where can I get help?

A: Check the Troubleshooting Guide or visit the CQL GitHub repository to report issues or ask questions.

Q: How do I contribute to CQL?

A: Visit the GitHub repository at azutoolkit/cql to report bugs, suggest features, or submit pull requests.