Re: Re: cvs: php4 /pear/Cache/Container db.php

Quoting Ulf Wendel <uw@netuse.de>: > No, we should not make things more complicated as they are. There're > already enough rules in PEAR. And please no mixed case for DB > fieldnames. Fine, make the case whatever you want. And I never said "thou shalt name all thy tables this way, or thou art a lout". I suggested it as a way to make sure that the fields didn't conflict with any reserved words in any databases. If you don't care about things working with any database other than mysql, it's a non-issue. > More important but the discussion on yet another (I'm sick of them) > coding rule Without some consistency, PEAR is simply not going to be as useful as it could be. I realize I'm probably pissing a lot of people off by harping about it, but I feel that someone needs to do it. If it means y'all come to loathe me personally, so be it. If you understand that I'm just doing it to try and keep this thing semi-coherent so that users won't be tripped up by things working differently for no apparent reason, all the better. It's nothing personal on my part. > is in my eyes the question where to place SQL snippets. SQL > snippet should not be hidden in the (doc) comments. I suggest having > cache_mysql.sql, cache_xy.sql files in Cache/. Why not both? Having them in the doc comments means that they'll show up in the online docs whenever we get our act together and have a browsable PEAR documentation tree up, which is a good thing. But I agree that having .sql files for easy use in table creation would be a good thing. -chuck -- Charles Hagenbuch, <chuck@horde.org> "We have no fuel on board, plus or minus 8 kilograms." -A NASA scientist