So, I was upset, it can happen right?! Now, if you would kindly go to this page:

<blah>

and answer the few questions there, I'd really appreciate! 8-)

We got (4,3), let's see whether it get saved properly...

No really, what's the problem with you??? Still wondering about this or what???

And I thought it was for the Drupal modules...

Oh well... Maybe I'll fix that later.

Ada variables are complex objects. When developing a compiler, you must definitively take that in account. You have several sides to your variables: one you need to be able to handle dynamic variables since the compiler will have to be capable of doing all the operations on all the constant variables just as if you were executing your program and it has to handle all the tests necessary to ensure integrity.

So... we need a library that can handle integers, a library to handle floating points, a library to handle arrays, etc.

Today, I had to fix an installation of MySQL.

There were several problems, and I finally got it to work. Somehow, I had to run some commands manually to cleanly shutdown the cluster server and then re-run the configuration script with dpkg:

Today, as I was working with Coverity, I got this one message...

Negative constant passed to a negative sink.

Although I understood the meaning, I thought that this message was very confusing, How about:

Unexpected negative value in parameter #<position>

title 1

Test A

title 2

Testing B

title 3

Weird format

Since I manage multiple computers and each run a PostgreSQL database system, I can see discrepancies between versions. (i.e. newer versions fix problems in older versions.)

One is in regard to the VACUUM FULL function. A properly installed PostgreSQL system is expected to run a VACUUM command every now and then on each of your database system. That function is a defragmenter, if you wish. It goes through your clusters and remove empty space (i.e. deleted nodes, logs, aggregator items, etc.) and moves data that is accessed more to the start of your file which can be accessed faster than the ...

Today I ran in an error that looked like this:

Invalid argument supplied for foreach() in <path>/modules/taxonomy/taxonomy.module on line 1214.

The line number may vary depending on the version you are using. At the time, I had Drupal 6.14 and the line number was 1214.

The problem is with a node that has an invalid definition of its taxonomy field. In other words, the $node->taxonomy is not defined. If it were an empty array, the function would not fail.

I was updating a new Drupal website from an old static website generating nodes automatically with a little module. There were a ...