Planet MySQL

Why a new memory engine may change everything ?

+1

-1

posted by Cedric PEINTRE on Mon 26 Sep 2011 16:00 UTC
Tags:

(edit) engine, blob, Percona, temporary table, admin, mariadb, text, max_heap_table_size, tmp_table_size, dynamic row format, memory engine

I’m sure you are aware that the last Percona server release includes a new improved MEMORY storage engine for MySQL.
This new engine is based on Dynamic Row Format and offers some of great features, specialy for VARCHAR, VARBINARY, TEXT and BLOB fields in MEMORY tables.

But because this new MEMORY engine by Percona has some limitations and because Percona server hasn’t used it for its internal temporary tables yet, I would like to talk about what can be the real benefits to have a brand new MEMORY engine based on Dynamic row format specialy for internal memory

[Read more...]

Federated Tables

+0

-0

posted by Mark Grennan on Wed 07 Jul 2010 15:55 UTC
Tags:

(edit) mysql, engine, tables, data, federated, Tips & Tricks, remote server

Your searching for how to create a join across two databases on two different servers and it can’t be done directly. select d1.a, d2.b from db1@server1 join db2@server2 where db1.c = db2.c; does not work.

You learn about federated databases. The federated storage engine allows accesses data in tables of remote databases. Now how do you make it work?

1) Check if the federated storage engine is supported. Federation is OFF by default!

mysql> show engines;
+------------+---------+----------------------------------------------------------------+
| Engine     | Support | Comment                                                        |
+------------+---------+----------------------------------------------------------------+
| InnoDB     | YES

+2

-0

posted by Stefan Hinz on Mon 23 Nov 2009 16:56 UTC
Tags:

(edit) mysql, sun, plugins, university, engine, storage, sharding, spider

This Thursday (November 26th, 14:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. This session was originally scheduled for October 15th but had to be postponed for technical reasons.

Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with multiple

+0

-0

posted by Stefan Hinz on Mon 23 Nov 2009 08:56 UTC
Tags:

(edit) mysql, sun, plugins, university, engine, storage, sharding, spider

This Thursday (November 26th, 14:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. This session was originally scheduled for October 15th but had to be postponed for technical reasons.

Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with

+0

-0

posted by Stefan Hinz on Mon 23 Nov 2009 08:56 UTC
Tags:

(edit) mysql, sun, plugins, university, engine, storage, sharding, spider

This Thursday (November 26th, 14:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. This session was originally scheduled for October 15th but had to be postponed for technical reasons.

Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with

[Read more...]

OQGRAPH at OpenSQL Camp 2009, Portland

+0

-0

posted by Open Query on Fri 13 Nov 2009 23:35 UTC
Tags:

(edit) mysql, Conferences, engine, opensqlcamp, open query, mariadb, graph, GRAPH engine, OQGRAPH

Antony is travelling up to Portland for this great event that’s about to start Fri evening and going over the weekend. He’ll be showing other devs and people more about the OQGRAPH engine, and gathering useful feedback.

Open Query is, together with many others (I see Giuseppe, Facebook, Gear6, Google, Infobright, Jeremy Cole, PrimeBase Technologies, Percona, Monty Program, and lots more), sponsoring the event so that it’s accessible for everybody – reducing the key factor to getting there rather than having to worry about high conf fees.

Having acquired the world’s biggest jetlag flying to Charlottesville VA for last year’s OpenSQL Camp, I can confirm from personal experience that it’s a great event. While I can’t be there this time, I’m looking forward to hearing all about it!

OQGRAPH engine on MySQL University – 5 Nov 2009 10:00 UTC

+0

-0

posted by Open Query on Tue 03 Nov 2009 12:48 UTC
Tags:

(edit) mysql, engine, open query, mysql university, mariadb, graphs, graph, GRAPH engine, trees, graphengine, OQGRAPH, hierachies

Only a few weeks after Walter’s session on Multi-Master Replication with MMM and thanks to the great gang at MySQL Docs (my colleagues from long ago!) I’ll be doing a MySQL University session in a few days, about the GRAPH computation engine. From talks/demos I’ve done about it so far, I’ve learnt that people love it but there are lots of interesting questions. After all, it’s a pretty new and in a way exotic thing.

MySQL University uses DimDim, an online presentation service. You’ll see slides, and hear my voice. You can also type questions in a live chat room. We actually even got desktop sharing working so a live demo is possible, we’ll see how that goes on the day (I’ll make sure to

+0

-0

posted by Stefan Hinz on Tue 03 Nov 2009 08:47 UTC
Tags:

(edit) mysql, sun, university, engine, storage, graph, computation

This Thursday (November 5th, 10:00 UTC - note the different time for this session!), Arjen Lentz of Open Query will present the brand new GRAPH computation engine for MySQL.

From the abstract: Most of us have had to deal with hierarchies (trees) and graphs (such as friend-of-a-friend style problems), and have thus learn that this is -at best- a bit of a monster to do in an SQL/RDBMS. Until now. The GRAPH engine (GPLv2 licensed) is a MySQL storage engine allowing hierarchies and more complex graph structures to be handled in a relational fashion. In a nutshell, tree structures and friend-of-a-friend style searches can now be done using standard

+0

-0

posted by Stefan Hinz on Tue 03 Nov 2009 00:47 UTC
Tags:

(edit) mysql, sun, university, engine, storage, graph, computation

This Thursday (November 5th, 10:00 UTC - note the different time for this session!), Arjen Lentz of Open Query will present the brand new GRAPH computation engine for MySQL.

From the abstract: Most of us have had to deal with hierarchies (trees) and graphs (such as friend-of-a-friend style problems), and have thus learn that this is -at best- a bit of a monster to do in an SQL/RDBMS. Until now. The GRAPH engine (GPLv2 licensed) is a MySQL storage engine allowing hierarchies and more complex graph structures to be handled in a relational fashion. In a nutshell, tree structures and friend-of-a-friend style searches can now be done using

+0

-0

posted by Stefan Hinz on Tue 03 Nov 2009 00:47 UTC
Tags:

(edit) mysql, sun, university, engine, storage, graph, computation

This Thursday (November 5th, 10:00 UTC - note the different time for this session!), Arjen Lentz of Open Query will present the brand new GRAPH computation engine for MySQL.

From the abstract: Most of us have had to deal with hierarchies (trees) and graphs (such as friend-of-a-friend style problems), and have thus learn that this is -at best- a bit of a monster to do in an SQL/RDBMS. Until now. The GRAPH engine (GPLv2 licensed) is a MySQL storage engine allowing hierarchies and more complex graph structures to be handled in a relational fashion. In a nutshell, tree structures and friend-of-a-friend style searches can now be done using

[Read more...]

GRAPH engine – Mk.II

+3

-0

posted by Open Query on Fri 16 Oct 2009 13:57 UTC
Tags:

(edit) mysql, Uncategorized, engine, social graph, open query, mariadb, graphs, graph, friend of a friend, GRAPH engine, hierarchies, hierarchy, shortest path, tree, tree traversal, trees

The GRAPH engine allows you to deal with hierarchies and graphs in a purely relational way. So, we can find all children of an item, path from an item to a root node, shortest path between two items, and so on, each with a simple basic query structure using standard SQL grammar.

The engine is implemented as a MySQL/MariaDB 5.1 plugin (we’re working on a 5.0 backport for some clients) and thus runs with an unmodified server.

Demo time! I’ll simplify/strip a little bit here for space reasons, but what’s here is plain cut/paste from a running server, no edits

-- insert a few entries with connections (and multiple paths)
insert into foo (origid, destid) values (1,2), (2,3), (2,4), (4,5), (3,6), (5,6);
-- a regular table to join on to
insert into people values (1,"pearce"),(2,"hunnicut"),(3,"potter"),

+1

-0

posted by Stefan Hinz on Mon 12 Oct 2009 16:24 UTC
Tags:

(edit) mysql, personal, university, engine, storage, spider

This Thursday (October 15th, 13:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with multiple backends in the server layer. This means that the data is accessible from any application without code changes. This

+0

-0

posted by Stefan Hinz on Mon 12 Oct 2009 09:24 UTC
Tags:

(edit) mysql, personal, university, engine, storage, spider

This Thursday (October 15th, 13:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with multiple backends in the server layer. This means that the data is accessible from any application without code changes. This

+0

-0

posted by Stefan Hinz on Mon 12 Oct 2009 09:24 UTC
Tags:

(edit) mysql, personal, university, engine, storage, spider

This Thursday (October 15th, 13:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with multiple backends in the server layer. This means that the data is accessible from any application without code changes.

+2

-0

posted by Artem Russakovskii on Thu 03 Sep 2009 15:00 UTC
Tags:

(edit) mysql, fulltext, Databases, enterprise, indexing, search, Programming, solr, sphinx, engine, comparison, server, compare, backend

In the past few weeks I've been implementing advanced search at Plaxo, working quite closely with Solr enterprise search server. Today, I saw this relatively detailed comparison between Solr and its main competitor Sphinx (full credit goes to StackOverflow user mausch who had been using Solr for the past 2 years). For those still confused, Solr and Sphinx are similar to MySQL FULLTEXT search, or for those even more confused, think Google (yeah, this is a bit of a stretch, I know).

Similarities

Both Solr and Sphinx satisfy all of your requirements. They're fast and designed to index and search large bodies of data efficiently.
Both

[Read more...]

TYPE= disappears again (MySQL 5.4.4)

+2

-7

posted by Open Query on Fri 17 Jul 2009 06:42 UTC
Tags:

(edit) mysql, Uncategorized, alter table, engine, CREATE TABLE, TYPE

I like the 5.4 developments, overall. It has useful stuff and is being developed and released a reasonable pace. Good progress. While perusing the MySQL 5.4.4 changelog, one particular change drew my attention, since it’s been (re)appearing since 2006. It’s the removal of the TYPE= keyword which was obsoleted since MySQL 4.1 in favour of the ENGINE= syntax in CREATE/ALTER TABLE.

While on the surface it may seem ok to remove the obsolete keyword, there are quite a few apps out there that use it, and that cannot be changed. So these will now be unable to use MySQL 5.4 or beyond. I filed this as a bug in 2006, MySQL bug#17501. If you’re interested in the “history of reappearance”, take a peek at the comments and their timeline. I just put in a

+2

-0

posted by Lenz Grimmer on Sun 21 Jun 2009 10:50 UTC
Tags:

(edit) mysql, Databases, Linux, embedded, innodb, OSS, suse, rpm, Compiling, engine, packaging

Oracle/InnoBase announced the availability of the embedded version of InnoDB at this year's MySQL Conference & Expo, but I have not seen a lot of comments or reviews about it so far. Which surprises me, because I think this is a very interesting piece of technology!

In my opinion it might actually hit the sweet spot for application developers seeking an alternative embedded database solution. SQLite is nice and popular, but it seems to have concurrency issues when used in multi-threaded applications. An embedded

+0

-0

posted by Toru Maesaka on Tue 16 Jun 2009 12:14 UTC
Tags:

(edit) mysql, OSS, engine, storage, drizzle, knowledge

Something I’ve added to BlitzDB recently that was pretty high on my todo list is support for variable width tables. So what is a variable width table? it is a table that contains columns that can vary in size, namely BLOB and TEXT types.

Going back to the basics, when a new row is to be written, a storage engine is given a pointer to the row data in MySQL format that it must somehow store for later lookup/retrieval. By meaning “somehow”, the storage engine is given the freedom to do whatever it likes with the row.

Writing a row for a fixed length table (a table with columns that are always the same size) is deadly easy. A storage engine can choose to not temper with the row and simply write or copy the data to it’s storage mechanism. This is because the storage engine is given a row that

+0

-0

posted by Toru Maesaka on Tue 12 May 2009 08:04 UTC
Tags:

(edit) mysql, OSS, engine, storage, drizzle, knowledge

I’ve decided to start a series of blog entries on not-so-obvious findings that I’ve found while working on my new project. By archiving the findings, I’m hoping that I can help those that are looking into developing a storage engine for the MySQL family in the future.

Accumulating these mini-knowledge would also be useful for me since I can refer back to it when I forget something. Also, once I write enough entries I’m planning on summarizing them and making it available on the Drizzle Wiki. If MySQL (http://www.mysql.com) is interested in updating the engine documentation, I would be more than happy to help there too.

So to begin with, I’ll describe something trivial that I stumbled across while trying to catch an error on duplicate primary key insertion to

+7

-0

posted by Giuseppe Maxia on Wed 29 Apr 2009 18:30 UTC
Tags:

(edit) mysql, performance, engine, partitioning, Testing, sandbox, spider

At the MySQL Conference 2009 I attended a session about the Spider storage engine, an engine with built-in sharding features.
The talk was notable for the speaker wearing a spiderman costume, and for some language barrier that made the talk less enjoyable than it should be. That's a pity, because the engine is very intriguing, and deserves some exploration.

What is the Spider engine, then? In short, it's an extension to the partitioning engine with the ability of connecting to remote servers. Basically, partitions + federated, except that Federated is explicitly removed during the compilation. Additionally, the spider

[Read more...]

Thoughts on tackling InnoDB’s auto increment

+0

-0

posted by Toru Maesaka on Fri 17 Apr 2009 10:28 UTC
Tags:

(edit) mysql, innodb, OSS, engine, drizzle

As I mentioned in my previous entry, InnoDB has it’s own auto increment counter which it uses to generate the next value for the database kernel (as we call it in Drizzle). At Drizzle project, we came across a suspicion that InnoDB doesn’t increment it’s internal counter on row updates. So what can this mean to you as a database admin?

Well, consider this simple table:

CREATE TABLE t1 (
    a INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
    val INT
) ENGINE=InnoDB;

and the following statements:

drizzle> INSERT INTO t1 (val) VALUES (1);
Query OK, 1 row affected (0.01 sec)
 
drizzle>

+0

-0

posted by Lenz Grimmer on Mon 12 Jan 2009 20:49 UTC
Tags:

(edit) mysql, Databases, Linux, OSS, community, conference, event, Presentation, meeting, cluster, engine, collaborating, OpenSolaris, FOSDEM

We've now concluded our call for papers for the MySQL Developer Room at FOSDEM 2009 in Brussels, Belgium, which will be open on Sunday, 8th of February from 09:00-17:00.

We received some excellent proposals and I am very excited about the schedule. Here's the quick summary of the talks:

Vladimir Kolesnikov: Practicing DBA's Guide to the PBXT Storage Engine
Kris Buytaert: Monitoring MySQL
Geert Vanderkelen: MySQL Cluster
Roland Bouman: MySQL 5.1 Plugins
Kaj Arnö: MySQL, powering and using Social Networks
Ewen Fortune: Percona MySQL patches and the XtraDB storage engine
Giuseppe

+0

-0

posted by Lenz Grimmer on Mon 12 Jan 2009 19:49 UTC
Tags:

(edit) mysql, Databases, Linux, OSS, community, conference, event, Presentation, meeting, cluster, engine, collaborating, OpenSolaris, FOSDEM

We've now concluded our call for papers for the MySQL Developer Room at FOSDEM 2009 in Brussels, Belgium, which will be open on Sunday, 8th of February from 09:00-17:00.

We received some excellent proposals and I am very excited about the schedule. Here's the quick summary of the talks:

Vladimir Kolesnikov: Practicing DBA's Guide to the PBXT Storage Engine
Kris Buytaert: Monitoring MySQL
Geert Vanderkelen: MySQL Cluster
Roland Bouman: MySQL 5.1 Plugins
Kaj Arnö: MySQL, powering and using Social Networks
Ewen Fortune: Percona MySQL patches and the XtraDB storage engine
Giuseppe

[Read more...]

A cool idea - Revision engine

+0

-0

posted by Giuseppe Maxia on Tue 30 Sep 2008 05:01 UTC
Tags:

(edit) mysql, engine, storage, revision

Yesterday I saw an announcement in the MySQL internals@ list, about a new storage engine being released. DDengine has created a revision engine, a sort of embedded proxy inside MySQL that keeps track of the changes you do to your data.
The idea is clever. You write to your table, update and delete without any concern, and the revision engine stores your changes in the background.
I wanted to tried the engine on my laptop (Mac OSX), but there was no binary available for this architecture. I contacted the authors and I received prompt assistance until I had the product installed. Unfortunately, it crashes immediately. Well, it's to be expected for a version 0.1.
I

[Read more...]

Running Drupal 6 on MySQL 6 using the Falcon Storage Engine

+0

-0

posted by Lenz Grimmer on Mon 28 Apr 2008 15:22 UTC
Tags:

(edit) mysql, Linux, OSS, community, installation, configuration, article, virtualization, drupal, hint, falcon, engine, cms

This article describes how to install the Drupal 6.2 CMS on MySQL (http://mysql.com/) 6.0, using the Falcon Storage Engine. The operating system is a default Ubuntu 8.04 "Hardy Heron" (x86) installation.

I will make a few assumptions here, in order to keep the instructions simple: a fresh OS install, no other MySQL databases or web services are running or have already been installed. Both MySQL and the web server are installed on the same host. You should be able to become root to install packages and to have access to the local file system and

+0

-0

posted by Lenz Grimmer on Thu 14 Feb 2008 20:55 UTC
Tags:

(edit) mysql, community, event, writings, Book, engine, contributing

IBM plans a residency to write a Redbook about the IBM DB2 for i5/OS as a Database Engine for MySQL:

Seize this opportunity to be among the first, elite IBM System i professionals worldwide to gain hands-on and practical experience with the MySQL on i5/OS. Working alongside and exchanging knowledge with some of the top database experts in the System i, you will develop a competitive edge that will serve you well in successful service delivery to System i clients. MySQL is used extensively with opensource PHP applications. As our customers deploy PHP web applications, many of

+0

-0

posted by Lenz Grimmer on Sun 22 Apr 2007 18:45 UTC
Tags:

(edit) mysql, OSS, community, conference, Presentation, meeting, Development, engine

Even though MySQL is used to power a lot of web sites and applications that handle large binary objects (BLOBs) like images, videos or audio files, these objects are usually not stored in MySQL tables directly today. The reason for that is that the MySQL Client/Server protocol applies certain restrictions on the size of objects that can be returned and that the overall performance is not acceptable, as the current MySQL storage engines have not really been optimized to properly handle large numbers of BLOBs. To work around these limitations, these projects usually just store a reference to the object (e.g. a path name in a regular file system). This approach works around the limitations applied by the MySQL Server, but results in a disconnection and potential source of inconsistency between the database and the [Read more...]

How to compile MySQL with the Falcon Storage Engine from the BitKeeper source tree

+0

-0

posted by Lenz Grimmer on Mon 08 Jan 2007 17:01 UTC
Tags:

(edit) mysql, Linux, Development, Compiling, hint, betatest, engine

Now that the source tree for the new Falcon Storage Engine is finally public, here's a quick HOWTO on how to compile the server from source. This procedure is described in more detail in the MySQL Manual. I assume you use Linux and have the required development toolchain installed.

You first should get the free BK client from http://www.bitmover.com/bk-client2.0.shar, unpack and install it:

$ wget http://www.bitmover.com/bk-client2.0.shar
--17:34:34--

+0

-0

posted by Lenz Grimmer on Mon 08 Jan 2007 17:01 UTC
Tags:

(edit) mysql, Linux, Development, Compiling, hint, betatest, engine

Now that the source tree for the new Falcon Storage Engine is finally public, here's a quick HOWTO on how to compile the server from source. This procedure is described in more detail in the MySQL Manual. I assume you use Linux and have the required development toolchain installed.

You first should get the free BK client from http://www.bitmover.com/bk-client2.0.shar, unpack and install it:

$ wget http://www.bitmover.com/bk-client2.0.shar
--17:34:34--

[Read more...]

Search

Profile

Top Voted (Last Week)

Top Voted (Last Month)

Top 20 Most Active Authors

Top 10 Most Active Team Blogs

Oracle MySQL Blogs

MySQL Links

Other Links

Planetarium

Similarities