BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or get video-only pass to recordings.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News InfoQ Article: DrySQL ORM for Rails

Building an Efficient Cloud Application Architecture (Live Webinar June 22, 2023) - Save Your Seat

InfoQ Article: DrySQL ORM for Rails

Bookmarks

Dec 14, 2006 less than one minute

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more

Bryan Evans of the DrySQL project felt that ActiveRecord falls a bit short of complying with the DRY principle. If you have tables or columns that aren't compatible with the naming conventions, then you need to redefine some of your database artifacts in application code. As well, ActiveRecord associations and validations are redundant specifications of database constraints. Bryan wants to be able to change his database schema without needing to re-wire the ORM layer(s) of dependent applications. He wants to avoid (as much as possible) the situation where he's averse to making a change to his database schema because of the effort that would be required to sync up dependent applications.

Since ActiveRecord uses the database's information schema to dynamically retrieve column metadata, Bryan asked: "Can this strategy be applied to all database artifacts?"

Read ORM with DrySQL and ActiveRecord

Rate this Article

Adoption
Style

This content is in the Database topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Clarification

    by Bryan Evans,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I should have been more careful in my description of validates_nullability_of. To clarify, this validation always rejects a null value, but the validation is only generated by DrySQL in situations where the DB would reject a null.

    Back to top
  • Re: Clarification

    by Sam Smoot,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    It might be interesting to see this work contrasted with Dr. Nic's "Magic Models" (magicmodels.rubyforge.org/).

    I haven't used either, but they seem to share some goals, so maybe a collaborative effort would be beneficial?

    Back to top
  • Typos in code snippet #1

    by Tyler Rick,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    This code snippet has the line:

    Employee bryan = Employees.find(18)

    1. The 'Employee' before bryan is unneeded and incorrect. (Might be correct in a *statically* typed language like Java where you actually have to declare variables... :) )

    2. Model names are singular: Employee.find(18)

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT