Heh. Amazon EC2 is having a major outage. It's been going on since
around 2:00am. Super major brokenness all over.
So much for elastic.
This brings to mind the recent discovery of the flaw in just-in-time assembly line production.
Just in time works just fine until japan as a whole goes off line and nobody's got any stockpile of parts anywhere in any warehouse and suddenly the entire manufacturing process of anything using parts coming from japan comes to a quick and grinding halt.
So now people are starting to rent warehouses not because they need to stockpile parts, but they need a buffer in case of disaster.
It looks like the amazon customers are learning this same lesson today.
make it a game...
no problems apart from that its an interpreted language where everybody wants to talk away the fact that this will be slower than native code.
just because of you store a pre-parsed copy of the interpreted code, thats no compiler. No body would call the zend-cache a JIT
Where I sit (and most people aren't like this, I'll admit) I'm tired of it all, I just want it to work.
why not? everything is a file. block devices are random access.
HA! That's funny. I hate fk constraints almost as much as I hate
stored procedures, but try explaining to a territorial dba (read: all
of them) that their fancy dancy constraints are fucking everything up.
The funny thing is, we don't use them at $workplace, as far as I can tell, we never have. This probably goes back to the dawn of time when HJM wrote all the code and did the DBA stuff himself. So it's become standard practice here, and now the DBAs are defending it because it's become defacto standard, and they don't want any inconsistency, or extra work, or to change the status quo, and they probably realize the advantages by now.
One of the reasons why I *like* our DBAs. (Well... sometimes ;) And it goes to show: if you don't like what your DBAs are doing, the solution is simple: be the Creator.
well. you get it for free, but it ain't free? Nobody whiping your ass for free? tell me more.
And... Once you caried truckloads of money to oracle to get their database, letting them educate you how to use it is about twice as expensive. And neither anybody from oracle will show up and get shit up and running as that article may sugest.
the Fn key that turns on and off the indicator lights still works. I think my motherboard is dead.
It's a Gateway MT3423, bought it in fall of 2007, so 2 1/2 years ago. Anyone know any way I can more thoroughly investigate the laptop to see if my motherboard is really dead? or do I just need to salvage it for parts and find a new laptop?
Right now I've removed the hard drive and put it in another laptop, an old Compaq Presario with a Pentium III and 184MB of RAM. Even Lubuntu is too much for this thing. When swapping out the hard drives, broke the connection between the touchpad and
motherboard in the old Compaq, so now I'm getting really friendly with keystrokes and when forced to using my USB mouse.
Many people hate them unfairly because either a) They've used one on a non-IBM that sucked because it was poorly made, b) They've used one on a computer that didn't have the proper drivers so it sucked or c) Both of the above.
cluster in a box. 512 atoms in 1/4 closet...
My Toshiba laptop has both a touchpad and a trackpoint, and I find myself using both, depending on what I'm doing. However, I also have a cordless notebook mouse that I use as well, which makes a lot of tasks easier to do than using the touchpad or the trackpoint.
One thing I just thought about though...My laptop can convert into a tablet.
There's a mini-joystick in one corner of the tablet which can perform some limited navigation: cursor up, down, left, right. It might've been more useful if there was a trackpoint there instead of the mini-joystick.
Everybody raves about git. That doesn't make it good or useful for my purposes, it just means everybody raves about it.
Everybody raves about windows, doesn't make it good, os/2 was superior
Telling git that I specifically want to commit something, as opposed to letting it figure it out seems a bit of a drag to me. Obviously to other people so they added the -a flag.
But again, I find value in having the repository be elsewhere, so by making my localdisk the repository of all versioning information (by default, I know it can sync else where, I haven't gotten to that yet) this seems less useful to me than cvs or svn.
What I liked a lot was that you can say switch to branch, and it just does. you can do that in cvs and you can't do that in svn and it drives me nuts.
registered me a number in less than 5 minutes and works.
I expected at least some small hiccups because of the vm but it works so far.
I haven't seen such a seamless install of anything since 1995 or so when I installed apple's digital camera software on windows 3.1
All these interesting possibilities...
Mar 31 2010 10:46am from Peter Pulse @uncnsrd
I see it from a different point of view.. if I am going to pay a
kazillion dollars for a database and people to run it, it damn well
better have referential integrity. That is one of the MAJOR selling
points of these systems isn't it???
Ok, well yes and no. It's a major selling point of RDBMS in general I agree with that. I don't agree that it's a major selling point of Oracle in specific, because it's become a very commoditized feature let's face it. Most of the major open source RDBMSs implement it... the value proposition of Oracle is further up the pyramid, with things like partitioning, and RAC, and replication, and all those fancypants SQL extensions, like analytical queries (some of which are standard ANSI SQL now, btw.)
In any case, foreign keys sometimes just don't work, because they can impose unpredictible lock orderings on your queries. Every time you issue DML on a constrained table, Oracle (and probably every other RDBMS suffers the same problem) spawns a child cursor/query against the parent/child tables to check indexes and enforce constraints. That child query creates the lock-order problem and as near as I've ever been able to tell, the ordering is simply undefined and can't be relied on.
So most likely FK constraints will work just fine for you for months or years, but eventually as your load creeps up and your schema becomes more complex and you have more and more disparate queries hitting it, you will start running into ORA-00060 (deadlock.) And most likely the problem is universal across RDBMS.
When this does happen, you can spend a lot of time scratching your head, analyzing Oracle dumps, and trying to fix your queries to consistify the locking order. But you will likely fail - so you either have to code around the ORA-00060 with retries, or just drop your constraints. Best not to go down the analysis route - it's so unlikely to work - just retry queries or drop constraints.
This is one reason you should never write code that DEPENDS on the presence on FK constraints in some what, particularly code that relies on CASCADE DELETE. Code must continue to function properly if the constraints have to be dropped, some day.