Showing entries 41476 to 41485 of 44050
« 10 Newer Entries | 10 Older Entries »
final prep on UC presentation (and new toy)

I bought a new toy yesterday (and about time I did). A Logitech presentation clicker thingy:

It has the laser pointer, the forward and backwards slide buttons and, arguably most interestingly, a built-in timer with vibrate alert.

What’s annoying is that the forward/back is done by page up and page down - and this doesn’t work for the “appear on click” thing for OO.org. Luckily for me, I just about never use that “feature” as the in version of OOo that Ubuntu ships in their stable release (5.04) is just too darn buggy in that area. I do sometimes wonder if people use the stable release of their product for any real work.

But it’s a nice little device and seems to be an improvement of the using the remote control feature of my phone to do the same thing (if you didn’t do …

[Read more]
Try to evaluate this yourself first

SELECT CONCAT(CONV(536,8,20), LPAD(EXPORT_SET(1,'Y','N','',1), 3, "P"), CHAR(32), HEX(234), UNHEX(594939469*POW(3,2)))

Then ask your server if you fail :-)

Overview of Server SQL Modes

One of the features that distinguishes MySQL 5 from it's predecessors is the increased ability to control how the server interprets SQL and how strict or relaxed it should behave towards errors. This is done by setting the server SQL mode.

Choosing an appropriate Server SQL Mode can be an important tool to ease the task of porting from database products like Oracle or Microsoft Sequal Server. Despite the terrific documentation on the MySQL Reference manual, I really felt the need to have some kind of quick reference around to make effective use of the server sql modes. So, I made up one myself:



Enjoy!

Sakila 0.8

After implementing feedback from the 0.7 version and fleshing out the documentation some more, I present the 0.8 version of the Sakila sample database. Feedback is always appreciated, especially regarding the documentation and the data itself regarding appropriateness and consistency.

Changes

  • Added actor_info view.
  • Changed error handler for inventory_held_by_customer function. Function now has an exit handler for NOT FOUND instead of the more cryptic 1329.
  • Added template for new BSD license to schema and data files.
  • Added READS SQL DATA to the procedures and functions where appropriate to support loading on MySQL 5.1.
  • Fixed date range issue in rewards_report procedure (thanks Goplat).

DOWNLOAD

Some MySQL XML utilities

Hi everyone,

I know it's next to nothing, but in case you happen to need it, I've got some XML-related MySQL utilities.



It's all as-is of course but this time, I explicitly included a couple of lines saying that the usage is all under GPL license.

Regarding the information_schema dump, there are some more tools in the works, among which is a xslt stylesheet that …

[Read more]
Gripe: PostgreSQL, MySQL 5, UNION and VIEW

As demonstrated in Gripe: MySQL 5 - a VIEW could replace a MERGE table, MySQL 5 falls a little short when it comes to using indexes in a VIEW containing UNION. So I've tried PostgreSQL out, and much to my chagrin (being a happy little MySQL developer from way back), Postgres handles indexes in this scenario perfectly. Doh!

Yet ultimately, I'm still up the proverbial creek. What I really want is the PostgreSQL query designer (equiv of MySQL query optimizer) coupled with MySQL's modular storage engine architecture, so FEDERATED tables could be used with a VIEW and a UNION as a form of distributed partitioning. Oh well. Back to the drawing board.

Nested repeating groups in MySQL query output

There are a lot of articles around that explain that relations (tables) should be normalized (an article by Mike Hillyer will get you started) before you can store them in a relational database. The complete normalization process consists of two steps:


  1. elimination of multi-valued attributes ('at most one value per column')
  2. elimination of redundancy ('no duplication of data')


Although these are two distinct activities that solve different problems, the methods used to perform them have a great deal in common. In both cases, some columns from the original table are moved to a new table, and a foreign key relationship is constructed to be able to relate the two tables.

The …

[Read more]
Something broken at the development source tree?

I just tried to upgrade my MySQL 5.1 server from the development source tree. Unfortunately, with no success.

First I tried to get the latest updates via BitKeeper, but the links seem to be broken: http://mysql.bkbits.net:8080/mysql-5.0 and http://mysql.bkbits.net:8080/mysql-5.1-new.

So I decided to download the latest nightly snapshot and got me the file http://downloads.mysql.com/snapshots/mysql-5.1/mysql-5.1.10-beta-nightly-20060415.tar.gz. I extracted the file with "tar xvfz mysql-5.1.10-beta-nightly-20060415.tar.gz" (which worked without problems) and changed into the just created directory. From there, I tried to compile the source code:

[Read more]
Code, refactoring, the meaning of OS2

The bulk of the OS2 code I removed last week, but since then I have found a few more thousand lines of code that needed to be removed. All of this is a rat's nest of #ifdef which will all soon to be gone. Its given me a good chance to look over a lot of code I have not touched in a while.

Inside of the MySQL server there are essentially three ports. Unix, Windows, and Netware. There are also remnants of DOS, VMS, UnixWare, and then a few other pieces laying around. Things like ifdefs around CYGWIN (which doesn't work, and we don't support it) and some pieces to support the old mit-pthreads library. Most of this is decently documented in the code but it is still there.

Why not just leave it?

1) More code for a new developer to look at and consider. An example is this is that I found an OS2 define in the new events code. I am sure that it was copied and pasted.
2) People will think it will work. …

[Read more]
Alternative privilege system including ROLES and separate host table?

I recently talked about the idea of a different privilege system that separates the host information from the user name. Of course, it would break backwards compatibility and so it's almost impossible to change the current behaviour entirely. Also, Beat Vontobel has suggested that there are situations where it is desireable to have user and host information combined.

However, there might be a (not too complicated) solution. I'm thinking of a separate database that manages the user privileges according to the alternative system. Stored Procedures and Triggers could sync the information in the new database to the mysql schema database - and maybe also the other way around. This would require no changes in the MySQL server at all and every user could decide for himself, whether or not to use the alternative system. And finally, the users managed by the new system should not …

[Read more]
Showing entries 41476 to 41485 of 44050
« 10 Newer Entries | 10 Older Entries »