Re: Excluding MySQL database tables from mysqldump

2014-04-07 Thread shawn l.green

Hello Tim,

On 4/4/2014 10:27 PM, Tim Johnson wrote:

* Tim Johnson t...@akwebsoft.com [140404 17:46]:

Currently I'm running mysql on a Mac OSX partition.

I have installed an ubuntu dual-booted partition and put mysql on
it. I have already set up a mysql user on the ubuntu OS.

In the past I have used mysqldump with just the --all-databases
option to transfer data across different linux partitions.

I'm wondering if I should explicitly exclude some of the tables from
the mysql database. If so, which? perhaps mysql.user?

thoughts? Opinions?
thanks

   I should add the following:

   1)the only user added to the new partition is the same as the
   primary non-root user on the Mac partition. Same credentials

   2)this is a workstation - it is closed to the outside world.

   FYI: ...



There are several ways to select which data you want in the backup. You 
can backup per-table, per-database, object type per database (routines, 
triggers), or global objects (events). What level of detail you want to 
copy from your old instance into your new instance is completely up to you.


--
Shawn Green
MySQL Senior Principal Technical Support Engineer
Oracle USA, Inc. - Hardware and Software, Engineered to Work Together.
Office: Blountville, TN

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: database not listed

2014-04-07 Thread shawn l.green

Hello Nicu,

On 4/6/2014 1:51 AM, Nicolae Marasoiu wrote:

Hi,

A directory in datadir does not show up as database. Please help!

drwx-- 2 mysql root 24576 oct  9 00:34 *opendental*
drwx-- 2 mysql mysql 4096 mar 22 19:54 performance_schema
drwx-- 2 mysql root  4096 mar 22 19:53 test


mysql show databases
 - \g
++
| Database   |
++
| information_schema |
| test   |
++
  \
Thanks
Nicu



At first glace, it appears that you have not copied the old 'mysql' 
database folder from your old --datadir location to the new one. MySQL 
only knows about the one active folder you have defined in your 
configuration file. It does not remember any older settings where you 
want your databases to be stored.


Remember to make the new files in the new data directory owned by the 
current mysql user and group.


Yours,
--
Shawn Green
MySQL Senior Principal Technical Support Engineer
Oracle USA, Inc. - Hardware and Software, Engineered to Work Together.
Office: Blountville, TN

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: Excluding MySQL database tables from mysqldump

2014-04-07 Thread Tim Johnson
* shawn l.green shawn.l.gr...@oracle.com [140407 07:05]:
 Hello Tim,
 
 On 4/4/2014 10:27 PM, Tim Johnson wrote:
 * Tim Johnson t...@akwebsoft.com [140404 17:46]:
 Currently I'm running mysql on a Mac OSX partition.
 
 I have installed an ubuntu dual-booted partition and put mysql on
 it. I have already set up a mysql user on the ubuntu OS.
 
 In the past I have used mysqldump with just the --all-databases
 option to transfer data across different linux partitions.
 
 I'm wondering if I should explicitly exclude some of the tables from
 the mysql database. If so, which? perhaps mysql.user?
 
 thoughts? Opinions?
 thanks
I should add the following:
 
1)the only user added to the new partition is the same as the
primary non-root user on the Mac partition. Same credentials
 
2)this is a workstation - it is closed to the outside world.
 
FYI: ...
 
 
 There are several ways to select which data you want in the backup. You 
 can backup per-table, per-database, object type per database (routines, 
 triggers), or global objects (events). What level of detail you want to 
 copy from your old instance into your new instance is completely up to you.

  I've run into other problems, such as a 

  1)running mysqldump exactly as I would have in linux and not
  getting all databases. Dunno why, but keep on reading.

  2)mysqldump forces all database names to lower case in the CREATE
  DATABASE statement. I know, one shouldn't use upper case in
  database names, but :) tell that to my clients.

  It turns out '2)' is a known problem in Mac, but I just didn't
  know it...

  My workaround was to write a python app that uses the MySQLdb
  module to get the name of all databases, iterate through the list
  and selectively operate on them, and ensure that proper case is
  used in the CREATE DATABASE command..

  So I'm good here, I think.
  Thanks much for the reply.

-- 
Tim 
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



MySQL Connector/ODBC 5.3.2 GA has been released

2014-04-07 Thread Hery Ramilison

Dear MySQL users,

MySQL Connector/ODBC 5.3.2 GA, a new version of the ODBC driver for
the MySQL database management system, has been released.

The available downloads include both a Unicode driver and an ANSI
driver based on the same modern codebase. Please select driver type
you need based on the type of your application - Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with any MySQL version since 4.1 (It will not work with 4.0 or
earlier releases.)

This is the third release of the MySQL ODBC driver conforming to the
ODBC 3.8 specification. It contains the minimally required
implementation of the standard with key 3.8 features, which include
self-identification as a ODBC 3.8 driver, streaming of output parameters
(supported for binary types only), support of the
SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver
only).

Also Connector/ODBC 5.3 introduces a GTK+-based setup library
providing GUI DSN setup dialog on some Unix based systems, currently
included in the Oracle Linux 6 and Debian 6 binary packages. Other new
features in the 5.3 driver are FileDSN and Bookmarks support.

The release is now available in source and binary form for a number of
platforms from our download pages at

   http://dev.mysql.com/downloads/connector/odbc/5.3.html

For information on installing, please see the documentation at

   http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-installation.html

Enjoy!

The MySQL Connectors team at Oracle

-

Changes in MySQL Connector/ODBC 5.3.2 (2014-04-08)

Functionality Added or Changed

  * Implemented support for the ODBCINSTGetProperties
interface for use by unixODBC GUI dialogs. This allows
users to configure a file DSN through a graphical user
interface on Unix-like platforms. (Bug #17513175)

  * Made the Connector/ODBC GUI on Linux comply with the
GNOME Coding Guidelines for Supporting Accessibility
(https://developer.gnome.org/accessibility-devel-guide/3.
10/gad-coding-guidelines.html.en).

  * Added support for the connection flag
DFLT_BIGINT_BIND_STR.

Bugs Fixed

  * The functions SQLSetDescField(), SQLGetDiagField(), and
SQLGetDiagRec() crashed when a null pointer was passed as a
handle for those functions. This fix makes the functions check
if the passed pointer is null before using it. (Bug #18431088)

  * SQLBulkOperations(SQL_FETCH_BOOKMARK) returned an SQL_NO_DATA
error when called after
SQLBulkOperations(SQL_UPDATE_BY_BOOKMARK) or
SQLBulkOperations(SQL_DELETE_BY_BOOKMARK). (Bug #18287216)

  * The order of the control elements was wrong during control
selection in Connector/ODBC's Windows GUI. (Bug #18240696)

  * Concurrent execution of SQLEndTran() and SQL_HANDLE_ENV
resulted in a segmentation fault. (Bug #18166331)

  * Calling SQLNumResultCols() with a NULL parameter resulted in a
segmentation fault. (Bug #18165197)

  * At a malloc() failure, Connector/ODBC crashed because in the
driver_new() function, driver is being freed before
driver-name and driver-lib. This fix corrects the order of
the free() calls. (Bug #17992912)

  * myodbc-installer did not initialize the allocated memory. This
fix flushes the buffer with \0 for initialization. (Bug
#18046120)

  * Connector/ODBC's GUI dialog could not be opened from within
ODBCManageDataSourcesQ4 for editing an existing DSN. (Bug
#18046123)

  * Connector/ODBC crashed when trying to prepare a query after
connecting to the server with an invalid value for CHARSET.
This fix checks the CHARSET value and throws an error if it is
invalid. (Bug #17999659)

  * Driver and installer crashed when the path lengths supplied
were longer than 256 characters or when the option strings
were longer than 100 characters. This fix makes Connector/ODBC
return the proper errors instead. (Bug #17966018)

  * SQLFetch() crashed when executed using unixodbc versions
2.3.0, 2.3.1, or 2.3.2. (Bug #17857204)

  * A segmentation fault occurred in SQLSpecialColumns() if the
table name supplied was too long. This fix makes Connector/Net
throw a proper error for the situation. (Bug #17854697)

  * SQLGetData did not return correct length of the data when
retrieving data from an output parameter stream. (Bug
#17814768, Bug #70946)

  * When called after SQLParamaData, SQLGetData returned an error.
(Bug #17842966)

  * A segmentation fault occurred in SQLBulkOperations for an
SQL_UPDATE_BY_BOOKMARK if the prior fetch returned no records.
(Bug #17714358)

  * Data corruption occurred in SQLBulkOperations(), because in
the batch_insert() function, ptr_offset_adjust sometimes
pointed to an invalid memory location. (Bug #17714172)

  * While doing BULK INSERT into a table's time column using
Connector/ODBC, a syntax error was thrown if there was an hour
value larger than 99. This fix makes sure the proper error is