UDF writing to unix socket - segfaults?
I am writing a UDF for sending messages to a local daemon. I've been trying to make it use a UNIX socket, but it keeps segfaulting on connect() or sendto(). I have double and tripled checked everything, but I'm not finding anything. After a day or two, I finally decided to switch to UDP and writing to localhost instead, which works fine. I still feel writing to a UNIX socket ought to work and even if I've got a permission issue or similar, a segfault is not the appropriate handling. Any clues? -- Per Jessen, Zürich (16.5°C) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Error starting data node
Helo, I am receiving error when trying to start the data node. The configuration seems ok. Kindly help. *C:\mysql\bin>ndbd* *Unable to connect with connect string: nodeid=10,172.17.3.66:1186* *Retrying every 5 seconds. Attempts left: 12 11 10 9 8 7 6 5 4 3 2 1, failed.* *2012-08-07 18:19:20 [ndbd] ERROR-- Could not connect to management server, e**rror: ''* *Config.ini on management node :* [ndbd default] # Options affecting ndbd processes on all data nodes: NoOfReplicas=1# Number of replicas DataDir=C:/mysql/bin/cluster-data # Directory for each data node's data files # Forward slashes used in directory path, # rather than backslashes. This is correct; # see Important note in text DataMemory=80M# Memory allocated to data storage IndexMemory=18M # Memory allocated to index storage # For DataMemory and IndexMemory, we have used the # default values. Since the "world" database takes up # only about 500KB, this should be more than enough for # this example Cluster setup. [ndb_mgmd] # Management process options: HostName=172.17.3.66 # Hostname or IP address of management node DataDir=C:/mysql/bin/cluster-logs # Directory for management node log files NodeId=1 [ndbd] # Options for data node "A": HostName=172.17.3.69 # Hostname or IP address NodeId=10 MaxNoOfOrderedIndexes=1024 MaxNoOfAttributes=3000 # added 2012.7.20 [mysqld] # SQL node A options: HostName=172.17.3.68 # Hostname or IP address NodeId=60 [mysqld] # SQL node B options: HostName=172.17.3.67 # Hostname or IP address NodeId=61 *my.ini on management server* [mysql_cluster] # Options for management node process config-file=c:/mysql/bin/config.ini configdir=c:/mysql/bin/cluster-cache/ *my.ini on data node * [mysql_cluster] # Options for data nod process: ndb-connectstring=172.17.3.66 # location of the management server ndb-nodeid=10 Kindly help. I have looked at the configuration and things fine to me Regards, Aastha Gupta
Re: trouble with perl
Hi, This probably means you changed your MySQL libraries but didn't recompile or reinstall DBD::mysql, Usually this kind of issue is solved by reinstalling DBD::mysql in the same way that you previously installed it, so it can build against your current libraries. - Perrin On Mon, Aug 6, 2012 at 5:42 PM, Elim Qiu wrote: > To populate table for a perl forum, I got the following error: > > aMac:mwf elim$ perl install.pl > dyld: lazy symbol binding failed: Symbol not found: _mysql_init > Referenced from: > /Library/Perl/5.10.0/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle > Expected in: flat namespace > > dyld: Symbol not found: _mysql_init > Referenced from: > /Library/Perl/5.10.0/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle > Expected in: flat namespace > > My OS is Mac OS X 10.6.8 64 bit, Apple built-in perl is 5.10.0 (64bit) and > MySQL is newly upgraded to 5.5.27 MySQL Community Server (GPL) (64bit) > > I don't know how to make DBD:mysql work. Any idea is appreciated Maybe > I have to get mysql source and compile/install it with custom options? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: About character_set_*
Unless your effort is to convert all text strings to Mainland Chinese only ...Dont forget 'Locale' http://dev.mysql.com/doc/refman/5.5/en/locale-support.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > From: rja...@yahoo-inc.com > To: zzgang2...@gmail.com; mysql@lists.mysql.com > Date: Tue, 7 Aug 2012 11:55:15 -0700 > Subject: RE: About character_set_* > > The answer is long and involved... > http://mysql.rjweb.org/doc.php/charcoll > > > -Original Message- > > From: Zhigang Zhang [mailto:zzgang2...@gmail.com] > > Sent: Tuesday, August 07, 2012 3:25 AM > > To: mysql@lists.mysql.com > > Subject: About character_set_* > > > > Hello. > > > > > > > > As I know, when client send data to server, the encoding converting > > process > > is: > > > > > > > > character_set_client --> character_set_connection --> db table > > encoding. > > > > > > > > I think it is a short path than above way: > > > > > > > > character_set_client --> db table encoding. > > > > > > > > Why it is converted to "character_set_connection"? > > > > > > > > > > > > Yours > > > > Zhigang. > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/mysql >
Re: DECIMAL datatype automatically makes blank become 0
2012/08/04 23:14 -0400, Fred G I'm using MySQL 5.2 Workbench, and when I import a csv into MySQL, blank values become 0 when I define the datatype to be a DECIMAL (in our case (DECIMAL(12,2)). Since there is the potential for values to be 0, this poses a problem for us. I initially wanted to make all the DECIMAL values become VARCHAR(255), because I can still do inequality queries on this column if it is a VARCHAR, and VARCHAR does not mind blanks. It keeps them as is. MySQL does not do real CSV files, only its version of CSV-ish files. What do you mean "blank"? Is there really a character there, between separators, or nothing at all? In any case, I guess you mean NULL in SQL terms. In that case, MySQL insists on seeing NULL on no escape character, or \N, where escape character is \. If this is LOAD DATA, a trick that another used is helpful here, making use of letting LOAD DATA store in a user variable, and using SET to make it either the number or NULL: LOAD DATA (..., @DN, ) SET decField = IF(@DN = '', NULL, @DN); -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: query help
2012/07/31 15:02 -0700, Haluk Karamete So, in a case like this shop.orders.32442 shop.orders.82000 shop.orders.34442 It would be the record whose source_recid is shop.orders.82000. Why? Cause 82000 happens to be the largest integer. Now, if they are always 5-digit-long integers, try ending with ORDER BY SUBSTRING_INDEX(source_recid, '.', -1) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: About character_set_*
The answer is long and involved... http://mysql.rjweb.org/doc.php/charcoll > -Original Message- > From: Zhigang Zhang [mailto:zzgang2...@gmail.com] > Sent: Tuesday, August 07, 2012 3:25 AM > To: mysql@lists.mysql.com > Subject: About character_set_* > > Hello. > > > > As I know, when client send data to server, the encoding converting > process > is: > > > > character_set_client --> character_set_connection --> db table > encoding. > > > > I think it is a short path than above way: > > > > character_set_client --> db table encoding. > > > > Why it is converted to "character_set_connection"? > > > > > > Yours > > Zhigang. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.6 has been released
Dear MySQL users, MySQL Server 5.6.6 (Milestone Release) is a new version of the world's most popular open source database. The new features in these releases are of beta quality. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. Note that 5.6.6 includes all features in MySQL 5.5. An overview of what's new in MySQL 5.6 is available online at http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html For information on installing MySQL 5.6.6 on new servers, please see the MySQL installation documentation at http://dev.mysql.com/doc/refman/5.6/en/installing.html For upgrading from previous MySQL releases, please see the important upgrade considerations at http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html Please note that **downgrading** from these releases to a previous release series is not supported. MySQL Server 5.6 is available in source and binary form for a number of platforms from the "Development Releases" selection of our download pages at http://dev.mysql.com/downloads/mysql/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. Please note that the list of platforms for MySQL 5.6 has been adapted to the changes in the field: - Apple Mac OS X 10.6 and 10.7 on x86 (32 bit) and x86_64 (support for OS X 10.5 has been dropped), - Debian 6 on x86 (32 bit) and x86_64 (support for Debian 5 has been dropped), - RedHat Enterprise / Oracle Linux 5 and 6 on x86 (32 bit) and x86_64 (support for RHEL/OL 4 has been dropped), - SuSE Enterprise Linux 11 on x86_64 (support for SLES 10 has been dropped), - generic Linux (kernel 2.6) on x86 (32 bit) and x86_64, - FreeBSD 9 on x86_64 (support for FreeBSD 7 and 8 has been dropped), - Oracle Solaris 10 and 11 on Sparc (64 bit), x86 (32 bit) and x86_64, - Windows Vista, 7, and 2008 on x86 (32 bit) and x86_64 (support for Windows XP and 2003 has been dropped). Packages for specific Linux distributions are provided in the specific format (RPM or deb), in addition the generic tar.gz packages will fit these distributions. For RedHat-alike distributions like CentOS or Fedora, both the RedHat and the generic packages should work. If you are using a newer version of your operating system, its binary compatibility approach (supporting applications built for older versions) should ensure you can use MySQL 5.6. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing The list of all "Bugs Fixed" for 5.6.6 may also be viewed online at http://dev.mysql.com/doc/refman/5.6/en/news-5-6-6.html Due to mail size restrictions, several bug fix descriptions have been removed from this mail, just the bug numbers are kept, and some others have been shortened a bit. Please refer to the online manual for the full text. If you are running a MySQL production level system, we would like to direct your attention to MySQL Enterprise Edition, which includes the most comprehensive set of MySQL production, backup, monitoring, modeling, development, and administration tools so businesses can achieve the highest levels of MySQL performance, security and uptime. http://mysql.com/products/enterprise/ Enjoy! On behalf of the MySQL Build Team at Oracle, Joerg Bruehe = D.1.1. Changes in MySQL 5.6.6 (2012-Aug-7, Milestone 9) Binary Logging * Performance: The server now implements group commit for the binary log: Multiple commits are grouped in memory, then written and flushed to disk as a group rather than individually. This reduces the number of writes and flushes, improving performance of binary logging. Group commit works for all storage engines. InnoDB implements some optimizations to take advantage of group commit capability. These system variables were added in conjunction with group commit: + binlog_order_commits: Whether to commit transactions in the same order they are written to the binary log or permit them to be committed in parallel. + binlog_max_flush_queue_time: How long in microseconds to keep reading transactions from the flush queue before proceeding with the group commit. + innodb_flush_log_at_timeout: Write and flush logs every N seconds. Performance Schema Notes * The Performance Schema is now enabled by default. To disable it, set performance_schema=off at server startup. In addition, the Performance Schema now automatically sizes the values of several of its parameters at server startup if they are not set explicitly. For example, it sizes the parameters that control the sizes of the events waits tables this way. To see which parameters are sized under this policy, use mysqld --verbose --help and look for those with a defa
MySQL Connector/Python 1.0.5 beta has been released
Dear MySQL users, MySQL Connector/Python v1.0.5 is a new version of the pure Python database driver for MySQL. This is the first in a series of beta releases that will introduce users to new features and changes. This release is feature complete, but as a non-GA release is not recommended for use in production environments. MySQL Connector/Python version 1.0 is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions (greater than v4.1). MySQL Connector/Python v1.0.5 (beta) is available for download from http://dev.mysql.com/downloads/connector/python/#downloads (Note: not all mirrors may be up to date yet) A brief summary of changes in MySQL Connector/Python v1.0 is listed below. Please check the ChangeLog file inside the distribution for a more complete list of changes. Changes in MySQL Connector/Python v1.0.5 This section documents changes and Bug fixes that have been applied in MySQL Connector/Python since the development release v0.3.2. Functionality Added or Changed: * Adding support for time values with a fractional seconds part. A new example script microseconds.py was added to show this functionality. * Refactored the modules connection and protocol and created a new module network. The MySQLProtocol does not keep a reference to the connection object any more and deals only with creating and parsing MySQL packets. Network interaction is now done by the MySQLConnection objects (with the exception of MySQLProtocol.read_text_result()). * Added MySQLConnection.reconnect() which used to reconnect to the MySQL server. It accepts number of retries and a delay between attempts. * Added descriptive error codes for both client and server errors in the module errorcode. A new sub-package locales has been added, which currently only support English client error messages. * Added SQLMode class in the constants module, making it easier to use them. * Incompatible Change: The MySQLConnection.ping() method raises an InterfaceError when the MySQL server is not available. It can also optinally reconnect and accepts the same arguments as the reconnect() method. * Incompatible Change: The MySQLConnection.is_connect() method now returns True or False. It can be used to simply check whether a connection is available or not. * Incompatible Change: MySQLCursor.execute() does not return anything for single statement operations. Sending multiple statements will result in a generator object to be returned by MySQLCursor.execute(). The MySQLCursor.next_resultset() became obsolete and was removed and the MySQLCursor.next_proc_result() method has been renamed to MySQLCursor.proc_results(), which returns a generator object. The MySQLCursor.with_rows property can be used to check if a result could return rows. The multiple_resultset.py example script shows how to go through results produced by sending multiple statements. (Bug #14208326) * Incompatible Change: The method MySQLConnection.set_charset() has been removed and replaced by MySQLConnection.set_charset_collation() to simplify setting and retrieving character set and collation information. The MySQLConnection properties collation and charset are now read-only. (Bug #14260052) * Incompatible Change: The MySQLConnection methods unset_client_flag() and set_client_flag() have been removed. Use the set_client_flags() method instead using a sequence. (Bug #14259996) Bug Fixes: * Fixed MySQLCursor.executemany() when INSERT statements use the 'ON DUPLICATE KEY'-clause with a function like VALUES(). (Bug #14259954, Bug #65678) * Fixed cursor.CursorBase attributes description, lastrowid and rowcount to be read-only properties. (Bug #14231160) * Fixed and refactored mysql.connector.errors module. (Bug #14039339) * Fixed MySQLCursor.description so column names are Unicode. (Bug #13792575) * Fixed automatic garbage collection which caused memory usage to grow over time. (Bug #13435186) * Fixed setting time zone for current MySQL session. (Bug #13395083) * Fixed handling of errors after authentication for Python v3. (Bug #13364285) Documentation - The documentation is still being developed, and is included in the distribution under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and Bug reports: http://bugs.mysql.com/ Enjoy! On behalf of the MySQL Build Team, Kent Boortz -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: trouble with perl
Thanks Stillman Benjamin. The link is about the mismatch of 32/64 bit among mysql, perl and os processor but I don't have that issues. My system is missing DBD::mysql module, and I still have trouble with that. On Tue, Aug 7, 2012 at 6:49 AM, Stillman, Benjamin < bstill...@limitedbrands.com> wrote: > http://bixsolutions.net/forum/thread-18.html > > > -Original Message- > From: Elim Qiu [mailto:elim@gmail.com] > Sent: Monday, August 06, 2012 5:42 PM > To: mysql@lists.mysql.com > Subject: trouble with perl > > To populate table for a perl forum, I got the following error: > > aMac:mwf elim$ perl install.pl > dyld: lazy symbol binding failed: Symbol not found: _mysql_init > Referenced from: > /Library/Perl/5.10.0/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle > Expected in: flat namespace > > dyld: Symbol not found: _mysql_init > Referenced from: > /Library/Perl/5.10.0/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle > Expected in: flat namespace > > My OS is Mac OS X 10.6.8 64 bit, Apple built-in perl is 5.10.0 (64bit) and > MySQL is newly upgraded to 5.5.27 MySQL Community Server (GPL) (64bit) > > I don't know how to make DBD:mysql work. Any idea is appreciated Maybe > I have to get mysql source and compile/install it with custom options? > > > > Notice: This communication may contain privileged and/or confidential > information. If you are not the intended recipient, please notify the > sender by email, and immediately delete the message and any attachments > without copying or disclosing them. LBI may, for any reason, intercept, > access, use, and disclose any information that is communicated by or > through, or which is stored on, its networks, applications, services, and > devices. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/mysql > >
RE: trouble with perl
http://bixsolutions.net/forum/thread-18.html -Original Message- From: Elim Qiu [mailto:elim@gmail.com] Sent: Monday, August 06, 2012 5:42 PM To: mysql@lists.mysql.com Subject: trouble with perl To populate table for a perl forum, I got the following error: aMac:mwf elim$ perl install.pl dyld: lazy symbol binding failed: Symbol not found: _mysql_init Referenced from: /Library/Perl/5.10.0/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle Expected in: flat namespace dyld: Symbol not found: _mysql_init Referenced from: /Library/Perl/5.10.0/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle Expected in: flat namespace My OS is Mac OS X 10.6.8 64 bit, Apple built-in perl is 5.10.0 (64bit) and MySQL is newly upgraded to 5.5.27 MySQL Community Server (GPL) (64bit) I don't know how to make DBD:mysql work. Any idea is appreciated Maybe I have to get mysql source and compile/install it with custom options? Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
About character_set_*
Hello. As I know, when client send data to server, the encoding converting process is: character_set_client --> character_set_connection --> db table encoding. I think it is a short path than above way: character_set_client --> db table encoding. Why it is converted to "character_set_connection"? Yours Zhigang.
