If your application does not catch the exception thrown from the PDO constructor, the default action taken by the zend engine is to terminate the script and display a back trace. This back trace will likely reveal the full database connection details, including the username and password. It is your responsibility to catch this exception, either explicitly (via a catch statement) or implicitly via set_exception_handler().
The default behavior in case of database problems is to display the host, username and password in the browser? Good grief.
Hi. Saw your comment on engadget earlier today - nice work. Would be great to see the basics: * cat/proc/cpuinfo * df -h * free * lspci (or cat/proc/bus/*/devices) * lsmod * dmesg etc
Was X using the framebuffer or an optimized driver?
Here's what you said: "Personally I think being able to resize brushs is missing. Quite often I'll need a slightly larger/smaller brush, but I can't resize it."
Resizing brushes is NOT missing. You CAN resize it.
If you just want it to be EASIER like it is in photoshop, then SAY THAT. Thanks.
Penny Arcade is the worst advertisement for Rails there is. I'm surprised the 37 signals guys haven't done a freebie consulting job to get their shit straight. (or maybe they have and PA is a simply realistic example of RoR under load...)
Every Inquirer story I've clicked through to from slashdot has been subsequently debunked. Anyone got independant verification of this startling discovery?
AJAX? Agile web? Sorry guys - sooo 2005. The zeitgeist has morphed already. Words like Rails, Blog, AJAX, Agile will draw only ridicule. Get over yourselves.
Adding a ten minute extension wouldn't really solve this.
The local ebay clone (doing quite well for itself - sold for ~ US$400mil this year) has had auto-extend for some time. The period is two minutes. It has virtually eliminated sniping (provided the auction is set to end at a normal time and not in the middle of the night). Sellers love it, buyers hate it - I do wish ebay would adopt it.
You're right of course - need to backup the current log as well.
PostgreSQL is tantilisingly close. It just needs to be easier. And available per-database instead of per-server.
There are ways to achieve this, eg Slony with it's new "log shipping" feature. But that has additional cruft like requiring every table in the database to be listed in a config file and unique primary keys actually ADDED to any tables which don't already have them.
Good backups is the only thing keeping me (and a dozen large message databases) on Sybase.
PostgreSQL needs a reliable, well documented method for performing live incrememental backups. As in:
1) dump the whole database once a day 2) dump the transaction log every 5 minutes
You can then recover to any point give or take 5 minutes by loading the last full dump and each of the incrementals up to the point you need.
PostgreSQL ALMOST has this in the form of "Point In Time Recovery" but..
1) the documentation is incomplete - key details (like a definitive method for identifying the current log file) are missing. Check out the threads in the postgres-admin mailing list. It needs to be easier and users need to be 100% confident that they have the right set of files.
2) you can only backup and restore the whole server instance - ie ALL the databases at once. In practice this means you need a second server somewhere to do recovery on, then need to perform a complicated migration back to the primary server.
If backups don't really matter to you (or you're not running a transactional system) then PostgreSQL is fantastic. But if it's getting many updates a day and you care about recovery (so you're not boned when someone forgets the WHERE clause in a DELETE/UPDATE command) then it doesn't quite cut the mustard yet.
An official reference implementation backup & restore script would be a good start.
IIRC HDMI carries exactly the same data as DVI - just with extra bells and whistles like 7.1 audio. So you can convert DVI to HDMI with a cheap adapter.
I've never encountered corrupted data with mysql (It seems to be urban legend), and I have worked on tables with billions rows for two years.
SELECT MessageDate FROM Messages WHERE MessageID = 1072047; | 0000-00-00 00:00:00 |
Corruption or just complete lack of validation? I'll let you decide. (This column also has bogus data like month month >12 and day >31 - naturally I can't query for them though!)
And I'm pretty sure you can turn those statistic processes off in postgresql.conf:
Slashdot Mirror
That's very interesting indeed. I knew console sales were higher, but not 10x.
You can forgive producers for concentrating on the console market with numbers like that in their future.
The default behavior in case of database problems is to display the host, username and password in the browser? Good grief.
Hi. Saw your comment on engadget earlier today - nice work. Would be great to see the basics: /proc/cpuinfo /proc/bus/*/devices)
* cat
* df -h
* free
* lspci (or cat
* lsmod
* dmesg
etc
Was X using the framebuffer or an optimized driver?
Love the parting shot.
Here's what you said: "Personally I think being able to resize brushs is missing. Quite often I'll need a slightly larger/smaller brush, but I can't resize it."
Resizing brushes is NOT missing. You CAN resize it.
If you just want it to be EASIER like it is in photoshop, then SAY THAT. Thanks.
Hmm?
Ctrl-Shift-B (or Dialigs->Brushes)
Choose a brush, click the Edit button
Or just create a new one from scratch
Penny Arcade is the worst advertisement for Rails there is.
I'm surprised the 37 signals guys haven't done a freebie consulting job to get their shit straight.
(or maybe they have and PA is a simply realistic example of RoR under load...)
Hah! I forgot about that .sig - I have them hidden, usually.
For the record, no I still haven't read TFA. Though I did break my unwritten rule of not reading slashdot stories whose title ends with a "?".
Every Inquirer story I've clicked through to from slashdot has been subsequently debunked.
Anyone got independant verification of this startling discovery?
AJAX? Agile web? Sorry guys - sooo 2005. The zeitgeist has morphed already.
Words like Rails, Blog, AJAX, Agile will draw only ridicule. Get over yourselves.
The local ebay clone (doing quite well for itself - sold for ~ US$400mil this year) has had auto-extend for some time. The period is two minutes. It has virtually eliminated sniping (provided the auction is set to end at a normal time and not in the middle of the night). Sellers love it, buyers hate it - I do wish ebay would adopt it.
Yeah it's expensive. We get it. Do we really need a daily reminder?
Slashdot is getting to be as bad as the blogs *cough*joystiq*cough*kotaku*cough*
This is just fanboy-bait.
Modern PVR software attempts to do this trick. I'm afraid to try it in case it misses the end-of-advertising frame and buggers up the recording.
What a pity they couldn't engineer a power rail into the eSATA spec.
Nice :) Unfortunately there are only two real possibilities:
1) The game is never released. The idiots in charge finally can the project, like they should have five years ago.
OR
1) The game is released
2) 5 people buy it
3) 5000 people download it for a laugh and delete it 5 minutes later
You're right of course - need to backup the current log as well.
PostgreSQL is tantilisingly close. It just needs to be easier. And available per-database instead of per-server.
There are ways to achieve this, eg Slony with it's new "log shipping" feature. But that has additional cruft like requiring every table in the database to be listed in a config file and unique primary keys actually ADDED to any tables which don't already have them.
Good backups is the only thing keeping me (and a dozen large message databases) on Sybase.
Just to plug my favourite itch..
PostgreSQL needs a reliable, well documented method for performing live incrememental backups. As in:
1) dump the whole database once a day
2) dump the transaction log every 5 minutes
You can then recover to any point give or take 5 minutes by loading the last full dump and each of the incrementals up to the point you need.
PostgreSQL ALMOST has this in the form of "Point In Time Recovery" but..
1) the documentation is incomplete - key details (like a definitive method for identifying the current log file) are missing. Check out the threads in the postgres-admin mailing list. It needs to be easier and users need to be 100% confident that they have the right set of files.
2) you can only backup and restore the whole server instance - ie ALL the databases at once. In practice this means you need a second server somewhere to do recovery on, then need to perform a complicated migration back to the primary server.
If backups don't really matter to you (or you're not running a transactional system) then PostgreSQL is fantastic. But if it's getting many updates a day and you care about recovery (so you're not boned when someone forgets the WHERE clause in a DELETE/UPDATE command) then it doesn't quite cut the mustard yet.
An official reference implementation backup & restore script would be a good start.
.. sums it up nicely, I thought.
Those who like Redhat but don't want to pay for it?
IIRC HDMI carries exactly the same data as DVI - just with extra bells and whistles like 7.1 audio. So you can convert DVI to HDMI with a cheap adapter.
I'd be very surprised if that tool didn't have rate limiting built in.
Maybe you should try again? There is no forced reg (I don't recall every seeing one in fact) and the content is very good IMO.
SELECT MessageDate FROM Messages WHERE MessageID = 1072047;
| 0000-00-00 00:00:00 |
Corruption or just complete lack of validation? I'll let you decide. (This column also has bogus data like month month >12 and day >31 - naturally I can't query for them though!)
And I'm pretty sure you can turn those statistic processes off in postgresql.conf:
#
# Access statistics collection
#
stats_start_collector = true
stats_reset_on_server_start = true
stats_command_string = false
stats_row_level = false
stats_block_level = false
Coralcached link (3Mb)
Is it a spec for a document, or a software application? All this talk of "posting new content into the feed"..
p i-quick-guide.php
http://www.atomenabled.org/developers/tutorials/a
Someone needs to write a simple RSS->Atom migration guide, leaving out all the content-management crappola.