Finally had time to reply to this

Post #166,233 by drewk 7/27/04 1:58:41 AM Reply	Finally had time to reply to this And the reply is, "Yeah, no shit." Then don't scatter if-tests around. The reason it was written this way is that the devel database is not actually a complete snapshot of live. Lots of tables and some whole databases aren't there, so pages break horribly in the devel environment. This should of course be solved by replicating the rest of the db. Instead it was handled by adding a configuration option to the db class to over-ride devel mode and connect to the live server anyway. So the developer then had to track, "For this function I want a connection to the live db, for that function I want a connection to devel." That stops now. Devel is devel, and if it doesn't work in devel then you fucking fix it. For another you're likely to need at least 3 environments some day. (Development, staging, production.) ... That is very nice if you, for instance, want to give each developer their own machine with a customized installation to play with. Actually we've got four: Devel, where each developer has his own vhost and all db connections (starting tomorrow morning) are to the devel db. Stage, for testing (assuming we hire some testers [sub-rant deleted here]), which also (as of tomrrow morning) points to devel db. Cert, for QA (assuming we hire ... oh, I already went there) which points to live data. Live. === Implicitly condoning stupidity since 2001.
Post #166,234 by deSitter 7/27/04 2:04:24 AM Reply	Re: Finally had time to reply to this The thing is, devel needs full-time attention like live, and it never gets that, because it's junk (not really, but...) -drl
Post #166,369 by ben_tilly 7/27/04 8:10:11 PM Reply	That's backwards :-( The reason it was written this way is that the devel database is not actually a complete snapshot of live. Lots of tables and some whole databases aren't there, so pages break horribly in the devel environment. This should of course be solved by replicating the rest of the db... It sounds like changes have been made directly on live and never propagated back. Which means that you're walking on a highwire twice. Of course the way that you should do it is write scripts to update dev, and then when you're happy, run them against prod. That way dev either matches prod or is ahead of it. (Data, of course, gets copied from time to time from prod to dev.) But you know that. Convincing the rest of the company is your problem... Cheers, Ben To deny the indirect purchaser, who in this case is the ultimate purchaser, the right to seek relief from unlawful conduct, would essentially remove the word consumer from the Consumer Protection Act - [link\|http://www.techworld.com/opsys/news/index.cfm?NewsID=1246&Page=1&pagePos=20\|Nebraska Supreme Court]
Post #166,451 by drewk 7/28/04 9:32:26 AM Reply	Gosh, really? Remember, we didn't have a devel DB until recently. Building a new one from scratch takes one of our report servers out of the rotation for most of a day, so we've been copying stuff "as needed". Our other problem is that the one person who has access to make changes on the live DBs doesn't use the devel DBs at all. === Implicitly condoning stupidity since 2001.
Post #166,458 by ben_tilly 7/28/04 11:35:00 AM Reply	Gah. I wish that was unusual. :-( To deny the indirect purchaser, who in this case is the ultimate purchaser, the right to seek relief from unlawful conduct, would essentially remove the word consumer from the Consumer Protection Act - [link\|http://www.techworld.com/opsys/news/index.cfm?NewsID=1246&Page=1&pagePos=20\|Nebraska Supreme Court]

Welcome to IWETHEY!