Comments on: Using Constants in Rails Models

By: Bill Eisenhauer

Bill Eisenhauer — Tue, 16 Oct 2007 12:19:59 +0000

Yeah, I’ve had situations where I’ve added a model, then later deleted it, and thus broken the migration when it runs from an early version. However, you can easily add the model into your migration to fix the migration.

I think this is a matter of style and my preference is still to use model constants in the migration. It just seems more DRY and adds accuracy to your migration.

Thanks for your feedback!

By: Tom-Eric

Tom-Eric — Tue, 16 Oct 2007 08:41:04 +0000

You really shouldn’t use your models in your migrations. It’s now possible to break the migration file by modifying the model. You could solve this by placing the model in your migration file, but I’m not sure if that’s the best solution.

By: Bill Eisenhauer

Bill Eisenhauer — Thu, 09 Aug 2007 01:13:09 +0000

Marcin,

I actually went back to my original code and it was correct there. This means that it is either being stripped out by CodeRay or that there’s a combination of characters that make the slash not render.

Sorta makes you want to be cautious about the code you lift from a blog, eh? As always, one should know all of the code they deploy.

Thanks for the tip.

Bill

By: Julian Schrader

Julian Schrader — Wed, 08 Aug 2007 21:33:08 +0000

Thanks for your great tips! By the way: GeoKit has helped me a lot building Waschstrasse.info—thanks!

By: Marcin Olak

Marcin Olak — Wed, 08 Aug 2007 14:28:03 +0000

From Programming Ruby:

[...] a period (.0) appearing outside brackets represents any character except a newline [...]

Thus we need a backslash:
TO_FORMAT = /^[_a-z0-9+.-]+@[_a-z0-9-]+\.[_a-z0-9.-]+$/i

I know the code is for demonstration purposes only but still, we don’t want bugs to propagate throughtout the Internet from this magnificent blog :)

By: Marcin Olak

Marcin Olak — Tue, 07 Aug 2007 09:22:51 +0000

I like this technique. BTW. GeoKit rocks! :)