On 5/18/06, Ted Zlatanov <[EMAIL PROTECTED]> wrote:
On 10 May 2006, [EMAIL PROTECTED] wrote:
Oh well, I think replace_column() is more clear anyway. I'll add it
in the next version.
"replace" still has connotations of a permanent change. Why not
"remap"?
Too late, I already added it as rep
On 10 May 2006, [EMAIL PROTECTED] wrote:
> Oh well, I think replace_column() is more clear anyway. I'll add it
> in the next version.
"replace" still has connotations of a permanent change. Why not
"remap"?
Ted
---
Using Tomcat but need to
(I think this bounced the first two times...apologies if it's a triple!)
On 5/10/06, Uwe Voelker <[EMAIL PROTECTED]> wrote:
> Between "swap" and "exchange" I would prefer "exchange" too. But maybe
> "replace"?
Yeah, I like that better too. Of course, it occurs to me now that you
can already just
i like replace too. i think dealing with columns is far enough away that it wont be ambiguous with the replace that deals with rowsOn 5/10/06, Uwe Voelker
<[EMAIL PROTECTED]> wrote:> "Change" sounds like it alters the existing column in-place. How about
> swap_column() or exchange_column() instea
> "Change" sounds like it alters the existing column in-place. How about
> swap_column() or exchange_column() instead? I think I like "exchange" best.
Between "swap" and "exchange" I would prefer "exchange" too. But maybe
"replace"?
Generally I think this has a low priority, it was just an idea
On 5/10/06 3:31 AM, Uwe Voelker wrote:
> from the documentation about inheritance:
>
> # Change the "start" column into a datetime column.
> __PACKAGE__->meta->delete_column('start');
> __PACKAGE__->meta->add_column(start => { type => 'datetime' });
>
> Why not add a method change_column()
Hello,
from the documentation about inheritance:
# Change the "start" column into a datetime column.
__PACKAGE__->meta->delete_column('start');
__PACKAGE__->meta->add_column(start => { type => 'datetime' });
Why not add a method change_column() (and change_columns()) which
combines the two
