This day just had to come:
MySQL.com (the official site for the MySQL database) was compromised via (shocking!) blind SQL injection. A post was sent today to the full disclosure list explaining the issue and dumping part of their internal database structure.
What is worse is that they also posted the password dump online and some people started to crack it already. Some of the findings are pretty bad, like that the password used by the MySQL director of product management is only 4 numbers (6661) and also posted multiple admin passwords for blogs.mysql.com…
MySQL have not said anything about this attack, but we will post more details as we learn more about it.
I was fairly impressed with pgAdmin III when I first used it. It seems to be simple to use for anyone who can’t write their own SQL statements. I wasn’t too good and it and each time I execute a change in the database I have a feeling the world’s going to end. But one thing the pgAdmin III doesn’t do well is backup and restore.
(Using pgAdmin III for PostgreSQL. A screenshot.)
In the end it’s best to use the command prompt (or terminal) and in this really beginner tutorial, we’ll do a backup and restore using the command line.
1. Set PATH for PostgreSQL in Windows Vista
This guide assumes you install in ‘C:Program FilesPostgreSQL8.3’, the default installation directory. Continue reading “How to backup and restore in PostgreSQL”
Queryset-refactor branch was used to develop a major refactoring of the django.db.models.query.QuerySet class to fix a group of SQL problems and make SQL generation easier for database backends requiring customization. The branch was created on 13 September, 2007, and merged into trunk on 26 April, 2008 (in ).
More information on the wiki.
I don’t have time to explore these things right now but I sure will when my examinations are over.