[1.6] API for DB upgrades in plugins [dev: garvin]

Mark threads with "[2.0]" for discussions about features in the longer-term future, "[1.6]" is for short-term. This is not the place for general discussions or plugin or template requests. Only features that are approved to happen by the core team should be listed here for better structuring.
Locked
User avatar
garvinhicking
Core Developer
Posts: 30015
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

[1.6] API for DB upgrades in plugins [dev: garvin]

Post by garvinhicking » Sun Jan 02, 2011 10:47 pm

... discussion here ...
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/

User avatar
Timbalu
Regular
Posts: 4598
Joined: Sun May 02, 2004 3:04 pm

Re: [1.6] API for DB upgrades in plugins [dev: garvin]

Post by Timbalu » Mon Jan 17, 2011 1:11 pm

Well, if nobody else is starting, I'll do it then...

I asked Garvin having an API for DB upgrades in plugins in the future of serendipity german thread.
This is while I discovered some weired behaviours with some plugins over the past years.
Every plugin has its own methods to do an upgrade and not trying to fail. But this happens! Its hard to debug by the way. I definitely remember the statistic and the staticpage plugin failing in some cases.
What I would like to have is a more bulletproof method so we do not have to reinvent the wheel for every new plugin.
Hope that helps to explain what was my goal with my request.

Ian

Locked