It has been a while since I posted something. I’m running in to some technical difficulties with the series of posts I have been working on. Mainly that WordPress thinks it needs to make my example code invisible.
Obviously that isn’t very helpful, and I’m working on it.
What are the posts about, you ask (or maybe you didn’t, but I’ll tell you anyway)? I’m putting a few session together on parsing XML in MySQL and making it perform well.
Hopefully everything is worked out within a week.
A Note On Good Practice
Even though I’ve been developing for some time now it never ceases to amaze me how many people don’t comment in their code. Most of us have fallen into the trap of “the code is self explanatory.” Sure, sometimes it is: if you’re writing “Hello World.” Even that can be questionable at times.
I once interviewed a seasoned developer who, when asked about how they document, replied “I think code should be self documenting.” I wanted to slap my forehead and send them packing right away. Code is never self-documenting. Never. Especially when you go back to it 4 weeks later. And if you think it is self documenting, the poor sap who has to maintain your code doesn’t.
With that said, I would like to make a plea to all non-documenters out there with good reasons on why you want to document.
Why Document? Visual Resting Place
Great …
[Read more]Introduction
Fortran (FORmula TRANslating System) is a general-purpose, imperative programming language that is especially suited to numeric computation and scientific computing. History of FORTRAN can be tracked late 1953 when John W. Backus submitted a proposal to his superiors at IBM. The First FORTRAN compiler appeared in April 1957.
Some notable historical steps where:
Last week, a SSL connection security vulnerability was reported for MySQL and MariaDB. The vulnerability states that since MariaDB and MySQL do not enforce SSL when SSL support is enabled, it’s possible to launch Man In The Middle attacks (MITM). MITM attacks can capture the secure connection and turn it into an insecure one, revealing data going back and forth to the server.
Issue resolution in MariaDB is visible through the corresponding ticket in MariaDB’s tracking system (JIRA): https://mariadb.atlassian.net/browse/MDEV-7937
The vulnerability affects the client library of the database server in both MariaDB and MySQL. But, the vulnerability does not affect all the libraries, drivers or connectors for establishing SSL connections with the server.
The vulnerability exists when the connection to the server is done through the client …
[Read more]It’s been almost a year since I benchmarked MariaDB and MySQL on our good old 4 CPU / 32 Cores / 64 Threads Sandy Bridge server. There seem to be a few interesting things happened since that time.
Introduction
For the moment, the only engines that fully support encryption are XtraDB and InnoDB. The Aria storage engine also supports encryption, but only for temporary tables.
MariaDB supports 2 different way to encrypt data in InnoDB/XtraDB:
InnoDB Specified Table Encryption
Specified Table encryption means that you choose which tables to encrypt. This allows you to balance security with speed. To use table encryption, you have …
[Read more]Introduction
Causal consistency [1] is one of the consistency criteria that can be used on distributed databases as consistency criteria.
Distributed database provides causal consistency if read and write operations that are causally related are seen by every node of the distributed system in the same order. Concurrent writes may be seen in different order in diffrent nodes. Causal consistency is waker than sequential consistency [2] but stronger than eventual consistency [3]. See earlier blog for more detailed description on eventual consistency https://blog.mariadb.org/eventually-consistent-databases-state-of-the-art/.
When a transaction performs a read operation followed later by a write operation, even on different object, the first read is said to be causally ordered before the write. This is because the …
[Read more]Good bye bzr, welcome git!
After latest releases we moved development of MariaDB Connectors for C, ODBC and Java from launchpad to github.
The connector repositories can be found under https://github.com/MariaDB
Repository-Links:
Feel free to watch, fork and contribute!
This year is just about over. It’s almost time to welcome 2015. In celebration of a fun year of sharing Sphinx-things, let’s review 2014′s most popular posts. 1: Use Sphinx With MySQL This one leads by a huge margin. Not a surprise. Many MySQL users get frustrated with MySQL’s native fulltext search after hitting a [...]
High season is coming, how do you make sure that MySQL will handle the increased load? Stress tests could help with that, but it’s not a good idea to run them in a production environment. In this case Select_scan, Select_full_join and other MySQL counters could quickly give you an idea of how many queries are not performing well and could cause a performance degradation as the load goes up.
Select_scan from SHOW GLOBAL STATUS indicates how many full table scans were done since last MySQL restart. Scanning the entire table is a resource intensive operation. It also forces MySQL to store unnecessary data in the buffer pool, wasting memory and IO resources.
Full scan of a tiny table would be quite fast so missing indexes could stay invisible until the load rises or the dataset grows up. This could also be the case for developers who work with too small data sets on their dev boxes. To prevent performance issues all newly added …
[Read more]