Re: [phpesp-dev] soma changes

[Bishop B. <ph...@id...>]

> Well, it's completely controlable: only the superuser can do the
> update. If you're able to update the files on the webserver, I think
> you can be trusted to do the db updates as well, no? And a good admin
> never gives out the superuser password to somebody else :)

I'm not sure I was clear.  The super user account has access to  
survey-oriented functionality that's unavailable to survey designers.   
That implies that the super-user still maintains surveys, just of a  
higher caliber.  With the addition of this change, that person is now  
also responsible/able to upgrade the application.

In some circumstances, great; it's needed.  But in others, it's a  
separated concern that now has no separation.  My usage falls into the  
latter category.  I maintain the software and the server, but a client  
manages the surveys (deleting, cross-tabulating, etc.): I would not  
want the client upgrading the software willy-nilly.


> Wether you do them via web or manually, that's exactly the same.
> And there are no inputs from the user requested: because of the xml method,
> the update goes completely transparant, no matter which version you
> came from (the same goes for the prefix updates that are now possible).

There _is_ a user input: initiate the upgrade.  In my usage, I don't  
want the super user initiating an upgrade.  Sure, I can one off the  
code, but it seems to me the ability to upgrade should be a capability  
that can be assigned.


> I invite you to try it out first, before going into more details.
> (I tried a 2.0.2 update: worked fine. I tried a fresh install: worked
> fine).

I'll certainly try it out. :)

bishop

-- 
Bishop Bettini
ideacode, Inc.
(main) +1 919 341 5170 / (fax) +1 919 521 4100

Visit us on the web at:
ideacode.com          Professional software research and development
reviewmysoftware.com  Improve sales! Review your software before you release
bytejar.com           Solutions to those annoying development problems