I was talking with a client and the topic of password crypting
came up. From my background as a C coder, I have a few criteria
to regard a mechanism to be safe. In this case we’ll just discuss
things from the perspective of secure storage, and validation in
an application.

use a digital fingerprint algorithm, not a
hash or CRC. A hash is by nature
lossy (generates evenly distributed duplicates) and a CRC is
intended to identify bit errors in transmitted data, not
compare potentially different data.

Store/use all of the fingerprint, not just part (otherwise
it’s lossy again).

Even in times of a growing market of specialized NoSQL databases,
the relevance of traditional RDBMS doesn't decline. Especially
when it comes to the calculation of aggregates based on complex
data sets that can not be processed as a batch like
Map&Reduce. MySQL is already bringing in a handful of
aggregate functions that can be useful for a statistical
analysis. The best known of this type are certainly:

If you use MySQL with InnoDB (most everyone) then you will likely
see this error at some point. There is some confusion sometimes
about what this means. Let me try and explain it.

Let's say we have a connection called A to the database.
Connection A tries to update a row. But, it receives a lock wait
timeout error. That does not mean that connection A did anything
wrong. It means that another connection, call it B, is also
updating a row that connection A wants to update. But, connection
B has an open transaction that has not been committed yet. So,
MySQL won't let you update that row from connection A. Make
sense?

I normally don't do this. When I see someone write a blog post I
don't agree with, I often just dismiss it and go on. But, this
particular one caught my attention. It was titled PHP
vs Node.js: Yet Another Versus. The summary was:

Node.js = PHP + Apache + Memcached + Gearman - overhead

What the f**k? Are you kidding me? Clearly this person has NEVER
used memcached or Gearman in a production environment that had
any actual load.Back in the day, when URLs and filesystems had
a 1:1 mapping, it made perfect sense to have a web server
separate …

I've been involved in a number of interviews over the last few
weeks as a client has been loking for a MySQL DBA. When you are
looking for position as a DBA in a large scale environement there
are some very important things you have to know.

You absolutely must know a scripting language.
In a smaller environment this often isn't necessary. You will
live and die by this in a large environment. I asked every
applicant one specific question..if you had to change a mysql
server variable on a pool of 100 mysql servers how would you do
this? It's easy when it's one,two or even a dozen servers. just
log in, change the my.cnf and change it "on the …

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.