It's been a busy year for MySQL. Perhaps you've heard. Here are some recent improvements to the speed, scalability, and user-friendliness of the MySQL database and the InnoDB storage engine that we think deserve their own headlines. Now is a great time to beta test the 5.5 release and give feedback to the MySQL engineering team.
Hi everyone. I am not really a new member i was once a member using the handle despiragado.
I now wish to be identified with my new handle.
It's been a while i have last visited the forum to see whats happening. I guess a lot has happened. I will try to read up and keep up to date.
I am a... (3 Replies)
Hello,
I couldn't find an actual introduction thread, so I decided to just put this here.
I go by d0wngrade online. I have been programming in multiple languages for about 15+ years. I started with standard web design languages like HTML and CSS, but I then advanced from design to development... (2 Replies)
After doing a yum install mysql mysql-server on Fedora 14 I wasn't able to fully install the packages correctly. It installed MySQL 5.1. I was getting the following error when running the:
mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)... (3 Replies)
SQL::Translator::Producer::MySQL(3pm) User Contributed Perl Documentation SQL::Translator::Producer::MySQL(3pm)NAME
SQL::Translator::Producer::MySQL - MySQL-specific producer for SQL::Translator
SYNOPSIS
Use via SQL::Translator:
use SQL::Translator;
my $t = SQL::Translator->new( parser => '...', producer => 'MySQL', '...' );
$t->translate;
DESCRIPTION
This module will produce text output of the schema suitable for MySQL. There are still some issues to be worked out with syntax
differences between MySQL versions 3 and 4 ("SET foreign_key_checks," character sets for fields, etc.).
ARGUMENTS
This producer takes a single optional producer_arg "mysql_version", which provides the desired version for the target database. By default
MySQL v3 is assumed, and statements pertaining to any features introduced in later versions (e.g. CREATE VIEW) are not produced.
Valid version specifiers for "mysql_version" are listed here
Table Types
Normally the tables will be created without any explicit table type given and so will use the MySQL default.
Any tables involved in foreign key constraints automatically get a table type of InnoDB, unless this is overridden by setting the
"mysql_table_type" extra attribute explicitly on the table.
Extra attributes.
The producer recognises the following extra attributes on the Schema objects.
field.list
Set the list of allowed values for Enum fields.
field.binary, field.unsigned, field.zerofill
Set the MySQL field options of the same name.
field.renamed_from, table.renamed_from
Use when producing diffs to indicate that the current table/field has been renamed from the old name as given in the attribute value.
table.mysql_table_type
Set the type of the table e.g. 'InnoDB', 'MyISAM'. This will be automatically set for tables involved in foreign key constraints if it
is not already set explicitly. See "Table Types".
Please note that the "ENGINE" option is the preferred method of specifying the MySQL storage engine to use, but this method still works
for backwards compatibility.
table.mysql_charset, table.mysql_collate
Set the tables default charater set and collation order.
field.mysql_charset, field.mysql_collate
Set the fields charater set and collation order.
SEE ALSO
SQL::Translator, http://www.mysql.com/.
AUTHORS
darren chamberlain <darren@cpan.org>, Ken Youens-Clark <kclark@cpan.org>.
perl v5.14.2 2012-01-18 SQL::Translator::Producer::MySQL(3pm)
