Planet MySQL Planet MySQL: Meta Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 10 of 66 10 Older Entries

Displaying posts with tag: Technical (reset)

MariaDB 5.5.38 Overview and Highlights
+0 Vote Up -0Vote Down

MariaDB 5.5.38 was recently released (it is the latest MariaDB 5.5), and is available for download here:

https://downloads.mariadb.org/mariadb/5.5.38/

This is a maintenance release, and so there are not too many big changes of note, just a number of normal bug fixes. However, there are a few items worth mentioning:

  • Includes all bugfixes and updates from 5.5.38

read more

Compiling & Debugging MariaDB(and MySQL) in Eclipse from scratch - Part 3: "Running in Eclipse"
+4 Vote Up -0Vote Down

Introduction:

To run MariaDB from Eclipse we will actually create and install the tar.gz package resulting from compilation(See Part 2) in a separate directory, this will allow us to have MariaDB cleanly installed on a separate location and so it will be also easily possible to run it independently from Eclipse.

In these Blog posts series we assume:


yoda							as developer user
 

read more

Compiling & Debugging MariaDB(and MySQL) in Eclipse from scratch - Part 2: "Compile in Eclipse"
+2 Vote Up -0Vote Down

Section 2: "COMPILE MARIADB IN ECLIPSE"



2.1 Download and prepare sources folder

We will need a directory to use as our playground, if you create the user yoda in Section 1:

$ su - yoda
$ mkdir -p ~/playground

Download latest MariaDB 10 sources tar.gz and copy the archive into the above directory, you can latest sources from:

read more

Compiling & Debugging MariaDB(and MySQL) in Eclipse from scratch - Part 1: "Setup the building environment"
+0 Vote Up -0Vote Down
This guide will help you in compiling and debugging MariaDB (MySQL, Percona) within the Eclipse IDE on Linux and using cmake for source project preparation. It will be split in parts to keep each post lightweight and with a finite objective. At the end of reading this series of blog posts you should be able to:
  • Prepare for compilation any MariaDB (MySQL, Percona) source release based on cmake framework.
  • read more

    MariaDB 5.5.37 Overview and Highlights
    +0 Vote Up -0Vote Down

    MariaDB 5.5.37 was recently released (it is the latest MariaDB 5.5), and is available for download here:

    https://downloads.mariadb.org/mariadb/5.5.37/

    This is a maintenance release, and so there are not too many big changes of note, just a number of normal bug fixes. However, there are a few items worth mentioning:

    read more

    Resolving Error 1918, System Error Code 126, When Installing MySQL ODBC Driver
    +0 Vote Up -0Vote Down

    If you are installing MySQL ODBC Driver and encounter the following error:

    Error 1918. Error installing ODBC driver MySQL ODBC 5.1 Driver, 
    ODBC error 13: The setup routines for the MySQL ODBC 5.1 Driver 
    could not be loaded due to system error code 126: 
    The specified module could not be found. 
    ...\myodbc5S.dll).. Verify...

    Then you will need to install the Microsoft Visual C++ 2010 Redistributable Package (select the appropriate one for your OS architecture below):

    64-bit version:

    read more

    Improve your Stored Procedure Error Handling with GET DIAGNOSTICS
    +0 Vote Up -0Vote Down

    In a previous post, I discussed debugging stored procedures with RESIGNAL, which is of great value when troubleshooting errors raised by your stored procedures, functions, triggers, and events as of MySQL/MariaDB 5.5.

    However, as of MySQL 5.6 and MariaDB 10.0, there is GET DIAGNOSTICS, which can be used to get the exact error details as well.

    RESIGNAL just outputs the error, as it comes from the server, for instance:

    ERROR 1146 (42S02): Table 'db1.t1' doesn't exist

    read more

    Quickly Debugging Stored Procedures, Functions, Triggers, and Events with RESIGNAL
    +0 Vote Up -0Vote Down

    I was recently debugging a stored procedure and could not easily identify the underlying reason for why it was failing.

    It had a standard exit handler catch-all for SQLEXCEPTION, which was:

    DECLARE EXIT HANDLER FOR SQLEXCEPTION
    BEGIN
    SELECT ...;
    END;

    When there was an error, it didn't really output anything useful.

    As of MySQL 5.5, there is RESIGNAL:

    "RESIGNAL passes on the error condition information that is available during execution of a condition handler within a compound statement inside a stored procedure or function, trigger, or event."

    read more

    MariaDB 10 GTID Explained
    +1 Vote Up -0Vote Down

    MariaDB replication in general works as follows: on a master server, all updates to the database are written into the binary log as binlog events, a slave server connects to the master and reads the binlog events and applies the events locally to replicate the same changes as done on the master. A server can be both a master and a slave at the same time, it is thus possible for binlog events to replicated through multiple levels of servers.

    read more

    InnoDB Primary Key versus Secondary Index: An Interesting Lesson from EXPLAIN
    +1 Vote Up -0Vote Down

    I ran into an interesting issue today, while examining some EXPLAIN outputs, and wanted to share the findings, as some of this is undocumented.

    Basically, you can start with a very simple InnoDB table - 2 INT columns, Primary Key (PK) on the 1st column, regular index on the 2nd:

    CREATE TABLE `t1` (
      `id1` int(10) unsigned NOT NULL,
      `id2` int(10) unsigned DEFAULT NULL,
      PRIMARY KEY (`id1`),
      KEY `id2` (`id2`)
    ) ENGINE=InnoDB;

    The query is:

    SELECT id1 FROM t1;

    This is a straight-forward query with no WHERE clause.

    read more

    Showing entries 1 to 10 of 66 10 Older Entries

    Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

    Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.