> Your Rails app classes are accessible in migrations, so you can call the
> bit.ly link generator just like you would from the application itself.
Thanks for the info, did not know this before.
>
> At this point, stop asking questions and go write some migration code.
> If you run into troubl
Quee WM wrote:
> Also I posted the same question on the ruby forum and one suggestion so
> far is that
>
> For one-shot scripts that are not exactly migrations,
But this is exactly a migration. It gets the database from one
consistent state to the next. That's the definition of a migration.
>
Quee WM wrote:
> Aldric Giacomoni wrote:
>> That is true - but since he mentioned a bit.ly link, I thought it would
>> be different for every row.
>
> You are 100% right that it will be different for each row. With the help
> of others on this forum I have written a callback function which
> pr
Also I posted the same question on the ruby forum and one suggestion so
far is that
For one-shot scripts that are not exactly migrations, it should be an
acceptable way to use an external script. I find some weight in this as
well as what if I need to redeploy the same app on a new server, with
Aldric Giacomoni wrote:
> That is true - but since he mentioned a bit.ly link, I thought it would
> be different for every row.
You are 100% right that it will be different for each row. With the help
of others on this forum I have written a callback function which
provides me with a bitly link
Curtis Cooley wrote:
> On Wed, Jan 6, 2010 at 11:35 AM, Aldric Giacomoni
> wrote:
>> A migration is a Ruby script.
>> The Rails sugar helps you tell the application (for instance):
>> "Hey there! I need you to add a column to this table. And while you're
>> at it, check every row, and do this on
6 matches
Mail list logo
