On Wed, Jan 29, 2003 at 09:28:05AM +0100, Garvin Hicking wrote:
Thanks, your suggestions were very valuable to me. I think this is the way to be done. I will sit down the next weekend (where I'm on vacation, so a lot of free time) and walk through the code. If everything runs smoothly (which I suspect) we can talk about my implementation at the end of next week.
Great to hear that!
Are there any major changes I should wait to be done in the next days? I currently use 2.4.0-dev (latest CVS)...
2.4.0 release was supposed to be coming up soon, in early Feburary, but I haven't heard anything more about it for a while. Rabus - how is your user privilege stuff going ?
Another solution could be not to store the php-code in a database, but instead hard-code it into the script. This will lose additional complexity and abilities to customize code, but could be much safer.
I see no loss of customizing code, and it would actually become easier to manege. I don't get where you see the loss of complexity?
The loss of complexity would be, that phpMyAdmin Users (in auth-mode other than 'superuser') don't usually have access to the phpMyAdmin-Codebase. So they can't create their own transformations.
I see that differently, the average user that is just using PMA is not capable of writing much PHP anyway. If they are using it in just a small installation, they they would have full access to it anyway, and otherwise, they just ask their admin to put a new script in.
But I think the phpcode-in-database issue has been dropped of good reasons completely, so I don't waste my creativity on that any more. ;)
I've got exams this next week, then I'm away from computer for the weekend, and the week after that I'll be coding again.