MySQL 5.1 (or even 6.0)

scawa · Posted: Tue Feb 19, 2008 2:11 am Post subject: MySQL 5.1 (or even 6.0)

Is anyone working on an ebuild for MySQL 5.1.... Has been out a while and need some features in 5.1

Thanks
_________________
Boredom is a personal Defect
-- Lamar Stephens

drescherjm · Posted: Wed Feb 20, 2008 2:43 pm Post subject:

See here:

https://bugs.gentoo.org/show_bug.cgi?id=194561
_________________
John

My gentoo overlay
Instructons for overlay

scawa · Posted: Thu Feb 21, 2008 9:03 pm Post subject:

I see this in the bug tracker. But the conversation is rather greek to me. It doesn't tell me if or where it is available.

Stephen McConnell
_________________
Boredom is a personal Defect
-- Lamar Stephens

drescherjm · Posted: Thu Feb 21, 2008 9:06 pm Post subject:

Ahh, Sorry.

There are a few versions in portage:
http://gentoo-portage.com/dev-db/mysql-community

Although none are the current version 5.1.23.
_________________
John

My gentoo overlay
Instructons for overlay

scawa · Posted: Fri Feb 22, 2008 12:16 am Post subject:

There are hard masked. If I'm not mistaken they are found in the packages.masked file and could be commented out if you wanted to emerge them?

I guess I'll just use Postgress for those functions I need out of 5.1.... and wait till it gets out of being hard masked.

Thanks
_________________
Boredom is a personal Defect
-- Lamar Stephens

jonnevers · Posted: Fri Feb 22, 2008 1:31 am Post subject:

scawa · Posted: Fri Feb 22, 2008 1:53 am Post subject:

One of the features on MySQL5.1 and its Tablespaces is the ability to create a tablespace in a "specific" location. You can specify a folder it will build the associated tables in.

I'm creating a database that will extend over 1.7 TB (multiple hard drives). The ability to break the DB up in to specific tablespaces in specific locations is important.

I'm glad that it will be that easy to install MySQL 5.1. One of the frustrating things about Postgresql and it's JDBC drivers (even their JDBC 3.0) drivers is that they do not support transactions as nicely as MySQL 5.1 does (even though the Postgresql community had ragged and ragged on MySQL about it's lack of trigger, and Stored Procedure and foreign indexes as MySQL was growing into maturity....).

The specific thing that Postgresql JDBC drives down support is the statement.getGeneratedKeys() method... where any autokeys generated in an add or update transaction are returned in a resultset and one can then insert them back into the object to which they are associated. This is important. Then one doesn't have to perform a query to create a key and put it into the object before saving OR do a read of the object just created to get the autogenerated key to put back into the object..... It does much better in keeping your objects in line with the DB and also in commit/rollback processing....

Anyway, there are a bunch of more feature (MySQL 5.1 lets you use Java Stored Procedures -- sort of like Oracle), better triggers..... just to start.

Thanks for your answers....
_________________
Boredom is a personal Defect
-- Lamar Stephens