[development] schema API add column after

[Steven Jones]

Hi,

I'd imagine that you could only use the schema API when it's
available, so on your 6.x branch of your module. But isn't that when
the numbering format changed for update functions too? You should
always leave update hooks as is, unless they're buggy, right?

On Mon, Jun 9, 2008 at 7:12 PM, Ashraf Amayreh <mistknight at gmail.com> wrote:
> I'm a little confused here, the upgrade guide says how hook_update_N should
> use the schema API, does this apply to the already existing update hooks or
> to new ones only? Same goes for the update hook naming conventions that
> contain drupal major version and so forth, how does this affect the already
> existing update hooks from the module's 5.x version?
>
> On Mon, Jun 9, 2008 at 6:09 PM, Matej Svetlík <matej.svetlik at cetelem.sk>
> wrote:
>>
>> hello,
>>
>> why do you need to have table column at specified position?
>>
>> On Mon, 2008-06-09 at 14:48 +0300, Ashraf Amayreh wrote:
>> > Hello all,
>> >
>> > I have an alter statement where I add a column at a specified location
>> > "ALTER TABLE {example} ADD COLUMN def TEXT AFTER abc" in drupal 5.
>> >
>> > Checking the schema API I can't see an equivalent to specify the
>> > position of the new field, I guess it just appends it at the end of
>> > the table.
>> >
>> > Any way to work around this?
>> >
>> > --
>> > Ashraf Amayreh
>> > http://blogs.aamayreh.org
>>
>
>
>
> --
> Ashraf Amayreh
> http://blogs.aamayreh.org



-- 
Regards
Steven Jones