Planet phpMyAdmin

So today I checked out my vServer performance using the phpMyAdmin Status Monitor that I have coded last summer, because a user notified me that a certain webpage doesn't load.
I couldn't figure out the problem as the site loaded normally for me and the server wasn't overloaded, however somehow I ended up hammering on the refresh button in the server tab to check what MySQL processes were running because it was fun and interesting.


So then one process did appear that was currently sorting the results of a query. It looked like a candidate for optimization. So I threw it into the query analyzer.



My assumption turned out to be correct. This query is used to determine when the visitor last visited the website, and it took 0.3 seconds to execute. It happens to be run on every page visit of on of my websites.

So, being already in phpMyAdmin, I head over to the table in question and add an index for this field.

ALTER TABLE `cc_counter` ADD INDEX ( `ip` )

Now lets run this query again:

It looks like with start of the new year, people started to ask for phpMyAdmin's projects for GSoC 2012. Given that we have no information whether there will be Google Summer of Code this year and whether we will be chosen to participate, these questions look quite premature.

On the other side you can start contributing any time and if you are already known in the community, you might have better chance being accepted. So forget speaking about hypothetical GSoC projects for now and start fixing some bugs, which is something much more needed right now (given that 3.5 is in alpha state).

If you are looking for more information, we have basic facts for developers on our website, there is also a wiki page mentioning some tasks for junior developers.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

My last post about Flattr has received much more attention than I would expect from short rant, but the feedback forced me to think a bit more about the issue.

I guess that most of Flattr early adopters jumped in for getting some money for things they produce (regardless it is music, text, software or anything else). The initial setup required users to also give money to others and this limitation was later removed and now you can only receive money without giving anything out. In the beginning every now and they I've discovered some interesting thing to flattr, so I usually had to postpone it to next month to give at least some reasonable value. This way initial money people have put there circulated between users and on each transaction they were reduced by 10% fee, what could lead to natural reduction of money available in the system.

Flattr is of course trying to introduce new features to attract new users. Flattr-a-Twitter is probably nice thing, however I somehow did not really get on Twitter train and I think I never will. The new catalog looks nice, still I don't think I will spend time browsing it and looking for content there. So basically this adds nothing useful for me.

Another recent feature - thanking to people who have flattered your thing in last month is IMHO bad idea. I've always seen Flattr as simple way to give little money to lot of various things. In case everybody would send thank you email, it would become every month spam, which I would simply ignore.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

As phpMyAdmin is approaching to 3.5 release, it has come time to share about translations status. Same as with past releases, you can expect this "spam" every week or so.

The 3.5 release comes with lot of new strings, so it's some work to get to 100%. However some translators have already managed this and we currently have five translations on 100%:

• English (Great Britain)
• Russian
• Spanish
• Swedish
• Turkish

There are few which are really close to 100% and I hope they will get there soon:

• Danish
• French
• Japanese
• Slovenian

Just on next level is Czech, where I'm progressing quite slowly and would welcome help :-).

Was your language not mentioned? It's now perfect time to contribute to it.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

I just got confirmed my flight bookings for FOSDEM 2012, so I'm looking to meet all great people there again. This year we've again arranged there meeting of phpMyAdmin developers, now it also includes three new faces from last years GSoC.

As for my schedule I did not yet find time to check all the schedule, but what definitely sounds interesting for me is Open Mobile Linux Devroom and some talks in MySQL and Friends Devroom. Rest will be (as usual) scheduled on the fly as I meet people there. This year I decided to deliberately skip keysigning as last year I anyway did not manage to attend it and I expect this year to be equally busy.

In case you want to meet me there, just let me know, we can try to arrange something in free slots :-).

Filed under: Debian English Gammu Phpmyadmin Suse | 0 comments | Flattr this!

I just got confirmed my flight bookings for FOSDEM 2012, so I'm looking to meet all great people there again. This year we've again arranged there meeting of phpMyAdmin developers, now it also includes three new faces from last years GSoC.

As for my schedule I did not yet find time to check all the schedule, but what definitely sounds interesting for me is Open Mobile Linux Devroom and some talks in MySQL and Friends Devroom. Rest will be (as usual) scheduled on the fly as I meet people there. This year I decided to deliberately skip keysigning as last year I anyway did not manage to attend it and I expect this year to be equally busy.

In case you want to meet me there, just let me know, we can try to arrange something in free slots :-).

Filed under: Debian English Gammu Phpmyadmin Suse | 0 comments | Flattr this!

First phpMyAdmin's alpha release for 3.5 is out for some time and it's best time to start translating if you want to be on time for final release.

For information about translating, check our website, in short you can translate either offline (get file from Git, translate and post it to translations tracker) or use online translation system available here:

https://l10n.cihar.com/projects/phpmyadmin/

As you can see in the summary, there is lot of new or changed strings, many of the new ones coming from advisor. I suggest you to keep these as last to translate as there is quite lot of them and it is more important to have translated rest of application. The advisor messages are placed at the end of po file.

I believe we can reach good amount of complete translations by final release with your contributions!

PS: You can expect me again to publish translations stats on this blog as we're heading to release.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

First phpMyAdmin's alpha release for 3.5 is out for some time and it's best time to start translating if you want to be on time for final release.

For information about translating, check our website, in short you can translate either offline (get file from Git, translate and post it to translations tracker) or use online translation system available here:

https://l10n.cihar.com/projects/phpmyadmin/

As you can see in the summary, there is lot of new or changed strings, many of the new ones coming from advisor. I suggest you to keep these as last to translate as there is quite lot of them and it is more important to have translated rest of application. The advisor messages are placed at the end of po file.

I believe we can reach good amount of complete translations by final release with your contributions!

PS: You can expect me again to publish translations stats on this blog as we're heading to release.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

From what I can see on both my personal Flattr account (where was never really much going on) and on (more attractive) phpMyAdmin's profile, the amount of people using Flattr there goes down there every month. There was definitely big momentum when it has been introduced, many geeks saw it as great opportunity for making micro payments work. Maybe people who started to use it at beginning are slowly abandoning it (what is true for me as well) and new ones simply don't come that much or whatever else. Anyway I definitely don't have the big picture to see whether is global trend or just my project is more unlucky...

Filed under: English Phpmyadmin | 9 comments | Flattr this!

From what I can see on both my personal Flattr account (where was never really much going on) and on (more attractive) phpMyAdmin's profile, the amount of people using Flattr there goes down there every month. There was definitely big momentum when it has been introduced, many geeks saw it as great opportunity for making micro payments work. Maybe people who started to use it at beginning are slowly abandoning it (what is true for me as well) and new ones simply don't come that much or whatever else. Anyway I definitely don't have the big picture to see whether is global trend or just my project is more unlucky...

Filed under: English Phpmyadmin | 9 comments | Flattr this!

Some time ago I found out that ice (solid water) is a semi-conductor, like f.e. silicon and germanium. So this means that theoretically a diode or transistor can be made out of it, even at home with common products.

What follows is a back of the envelope reasoning, not a proof of concept, as I haven't tried it, but it might work.

First some rudimentary background about semi-conductors and how to make a simple component, like a diode or a transistor. A semi-conductor is basically an insulator that conducts electricity only in some circumstances, for instance when a semi-conductor is doped with another material to add electrons (negative, n-type) or to create 'holes' (positive, p-type), which can conduct electricity.
If a n-type semiconductor is joined by a p-type, you get a diode. If another p-type or n-type is added to create a npn or pnp-sandwich, you get a transistor.

So if frozen water (pure water (H2O), distilled) forms a semi-conductor lattice, it needs to be doped with something else to create the holes and electrons. More research is necessary to find suitable candidates, but for instance kitchen salt consists of sodium (Na) and chlorine (Cl) atoms which, when diluted in (pure) water, become positively and negatively charged ions.
By adding an electrical charge on two sides of the solution (pure water with f.e. a little bit of kitchen salt), most of the positively charged ions would be transfered to one side and the negatively charged ions to the other side. Freezing the solution at that moment would create an ice cube with a p-type and an n-type side, thus a diode.
Cutting a second diode ice cube in half and joining it with the other one, creating a npn or pnp sandwich results in a transistor.

This is just an idea, a lot of things need to be solved to make it work. For instance, what materials should be used to make n-type and p-type semi-conductors out of frozen water? How much of the material is needed? Will this work on a macroscopic scale (regular sized ice-cubes), or should the ice-cube be very tiny?
Where should the electrodes be positioned to separate the ions and what charge is necesarry?
Should the ions be evenly spread, and how can this be achieved?
And if it works, is it a practical diode? It would need subzero temperatures to remain solid, but it could melt by the heat dissipation of the electrical current flowing in the icy diode.

Due to the holidays this report has been slightly delayed ;-)
However, I'm happy to report that the gallery module is now mostly finished and only a number of smaller features are missing. Since the last report I've completed:
- Store/Restore image size and crop area
- All the server side code
- Default sizes from which the user can select from. This includes default sizes for the original image, the preview image and the crop area.
- Pictures can be deleted.
- There's now default sizes for the original and preview image which is a per-gallery setting.
- Drag&Drop image reordering is finally working too. I've had difficulties getting jQuery UI Sortable to work, the bug being wrong event bubbling.
- Added a very simple pagination for the blog (not related to the gallery module)
- A ton of bug fixing

The gallery module is now also being tested and running the gallery on my wife's website saraty.com. I was happy to hear that she is very pleased with the simplicity of setting up a gallery. Below is a screenshot of an image being edited.



Until the end of January the only things left to do are:
- There is one bug left to fix with image reordering
- Classic style file upload with file selection
- If there is time left, there could be some per-gallery-batch-image-resize so one could easily change all the preview and original image sizes.
- Write documentation.

For last few months I was unable to write a blog post due to various reasons. May be because of my laziness on writing blog post. But I felt to write a post as my last post in this year, about our final year project which was completed couple of months back.

• Store and restore the image size and cropped area so a user doesn't need to select it from anew if he wanted the picture just a bit bigger.
• Server code for cropping and resizing
• Allow image editing of both thumbnail and full size picture. For this I have already refactored the image editing code into a jquery plugin for it to be modular.

Since last update I've added a settings dialog for each image so users can change their properties such as description and thumbnail. This information is also saved and stored in database now.

Also I've found a great image cropping tool named Jcrop which I probably will be implementing until next time. I'm also considering to add a thumbnail resize feature like in this demo.

And finally I've been fixing a few bugs in the dialog code.

Today, while merging changes to phpMyAdmin from our translation server I was very surprised that we have two languages which already reached 100% - Slovenian and Turkish (and four more just few strings from 100%). The huge amount of new strings introduced during 3.5 development (mostly being MySQL advisor hints) made me thing it will take very long time till they all get translated, but I was proven wrong.

Anyway there is still lot of work to do, so feel free to join our translators team.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

Today, while merging changes to phpMyAdmin from our translation server I was very surprised that we have two languages which already reached 100% - Slovenian and Turkish (and four more just few strings from 100%). The huge amount of new strings introduced during 3.5 development (mostly being MySQL advisor hints) made me thing it will take very long time till they all get translated, but I was proven wrong.

Anyway there is still lot of work to do, so feel free to join our translators team.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

In this 2 weeks I've had to do some major refactoring of Anegos dialog code so that it allows multiple dialogs. This will be needed so e.g. one can open a gallery settings dialog while being in the edit mode.

In the process I had to touch a lot of code, so I also cleaned up much of the code style. I've also found a number of bugs that I fixed.

The progress on the Gallery itself though hasn't gone much further. I've made only small additions and until the last day I spent a lot of time getting jQuery UI Sortable working on the images so one can Drag&Drop them but I failed. There must be something bugged with that widget.

phpMyAdmin demo server got some updates recently. First of all I've updated MySQL and MariaDB version it uses (MySQL is now on 5.5.7 and MariaDB on 5.3.2).

Later I've finally found time to make mentions of demo server less intrusive and fit more in existing interface. I've used jQuery to inject information about demo server to main page as one of standard boxes. It fits there nicely and puts information on main page where most users land anyway (you can see it for example here). With most important information on main page, the other pages could be reduced and now only mentions demo server and Git revision it is using.

This brings user experience closer to real phpMyAdmin without intrusive information shown on top of every page. I hope you will like it :-).

Filed under: English Phpmyadmin | 0 comments | Flattr this!

phpMyAdmin demo server got some updates recently. First of all I've updated MySQL and MariaDB version it uses (MySQL is now on 5.5.7 and MariaDB on 5.3.2).

Later I've finally found time to make mentions of demo server less intrusive and fit more in existing interface. I've used jQuery to inject information about demo server to main page as one of standard boxes. It fits there nicely and puts information on main page where most users land anyway (you can see it for example here). With most important information on main page, the other pages could be reduced and now only mentions demo server and Git revision it is using.

This brings user experience closer to real phpMyAdmin without intrusive information shown on top of every page. I hope you will like it :-).

Filed under: English Phpmyadmin | 0 comments | Flattr this!

Unfortunately I couldn't find much time to invest on this Project so I will have to catch up within the following 2 weeks.

Po delší době jsem se rozhodl do blogu občas přispět i v českém jazyce, tentokrát trochu agitační.

V nové verzi phpMyAdmina bude mimo jiné poradce pro nastavení parametrů serveru, v podstatě obdoba MySQLTuneru a podobných nástrojů. Protože se seskládá z velkého množství pravidel, jedná se opět pro velkou práci pro překladatele. Což je i důvod proč sem píši - zatím většina jejich popisů není přeložena do češtiny a to je úkol, se kterým můžete (při znalosti technické angličtiny) pomoci. Stačí se zaregistrovat na překladový server a začít překládat.

Samozřejmě je záhodno dodržet stávající terminologii používanou v překladu, ale jsem nakloněn i připomínkám a úpravám v něm, stačí se mi ozvat.

Filed under: Czech Phpmyadmin | 0 comments | Flattr this!

Po delší době jsem se rozhodl do blogu občas přispět i v českém jazyce, tentokrát trochu agitační.

V nové verzi phpMyAdmina bude mimo jiné poradce pro nastavení parametrů serveru, v podstatě obdoba MySQLTuneru a podobných nástrojů. Protože se seskládá z velkého množství pravidel, jedná se opět pro velkou práci pro překladatele. Což je i důvod proč sem píši - zatím většina jejich popisů není přeložena do češtiny a to je úkol, se kterým můžete (při znalosti technické angličtiny) pomoci. Stačí se zaregistrovat na překladový server a začít překládat.

Samozřejmě je záhodno dodržet stávající terminologii používanou v překladu, ale jsem nakloněn i připomínkám a úpravám v něm, stačí se mi ozvat.

Filed under: Czech Phpmyadmin | 0 comments | Flattr this!

Translation server for phpMyAdmin and Gammu/Wammu has been updated to run latest Pootle. I had to do this upgrade to be able to run on latest Django, which is used by other websites as well (this blog is one of them).

Unfortunately it was not as easy as running apt-get upgrade as Pootle package has been dropped from Debian recently. So I had to make quick and dirty packages myself (no removal of embedded software and so on).

Installing newer version lead to major breakage as the database upgrade silently failed and I had to recover manually. In the end I've dropped all pootle_* tables and recreated them again. Unfortunately this lead to loss of some data from user profiles, but I could not see other way around.

Anyway the service should be now back running in normal shape, so go ahead and translate :-).

Filed under: Debian English Phpmyadmin | 0 comments | Flattr this!

Translation server for phpMyAdmin and Gammu/Wammu has been updated to run latest Pootle. I had to do this upgrade to be able to run on latest Django, which is used by other websites as well (this blog is one of them).

Unfortunately it was not as easy as running apt-get upgrade as Pootle package has been dropped from Debian recently. So I had to make quick and dirty packages myself (no removal of embedded software and so on).

Installing newer version lead to major breakage as the database upgrade silently failed and I had to recover manually. In the end I've dropped all pootle_* tables and recreated them again. Unfortunately this lead to loss of some data from user profiles, but I could not see other way around.

Anyway the service should be now back running in normal shape, so go ahead and translate :-).

Filed under: Debian English Phpmyadmin | 0 comments | Flattr this!

I'm on the bus back to the hotel, after a weekend of meeting and collaboration with a lot of inspired Open Source developers. We met at Google Headquarters for the annual GSoC Mentor Summit, discussing last year's Google Summer of Code in particular and Open Source collaboration in general. More than 300 people of 175 participating organisations, from all over the world, were present.

It was my first time, both as a GSoC mentor for the phpMyAdmin project as on attending the summit, but it was great (or awesome, like some would state it). I've met and talked with many people. I learned a lot from the different sessions I attended and was pleasantly surprised about how much drive, knowledge and experience was present.

Awesome!

Week 1
I've spent most time contemplating on how to build a good UI for the Gallery module and researching on HTML5 File upload. Since there is already existing libraries for Drag&Drop file upload I don't have to reinvent the wheel. However as this technology is fairly new, I guess not to many solutions exists for it yet. At least not as jQuery plugin, which for me is a must for better code quality. In particular I've been weighing the pros and cons of:

• jQuery filedrop: A basic do-it-yourself Drag&Drop file upload that only covers the actual uploading and lets the user implement all the UI related stuff.
• jQuery File Upload: A fully featured Drag&Drop file upload with GUI that has it all, but requires jQuery UI and the jQuery Templates plugin.

Starting from last week, I have begun a new project that will focus on 2 modules of my experimental content management system Anego CMS. This project will end not later than January 2011 due to the fact that this project will be part of my bachelor studies in software engineering.

Anego is a new, basic and still pretty unstable (in terms of backwards compatibility) cms that I have been working on for the last few years and is powering not only my website (tyron.at) but also my wife's (saraty.com), my brother's (simpleit.at) and any small business websites that I can make my customer (I've got 3 so far!) ;-)

My CMS is using a new model for representing a website page - it is broken down into elements that can be dragged and organized to the users preference. Each of these elements is seen as a "Content Element" plugin/module that users may add and remove to Anego.

There already exists a very basic blog module that allows the creation, editing and deleting of blog entries and a simple comment feature to each blog entry. My Job is it now to improve the blog module, that include the following points:
- Module Interface - The current implementation of module support within Anego is rather unstable, it may have to change quite substantially, thus any already written modules will need to be adjusted accordingly
- Pagination - Currently all blog entries are displayed in one page. Proper pagination needs to be added.
- Archive and Navigation - There currently no overview over the written blog entries, an intelligent way of displaying a list of blog entries needs to be found, as well as implementing archivation features (navigation by year/month or similar)
- RSS Feeds - A blog without RSS support is quite useless.
- Settings: A settings dialog for changing some basic properties such as commenting, entries per page, etc. should be added.
- Comment Anti-Spam and maybe signup by google/facebook/openid/etc: The current implementation of comments may be vulnerable to spam
- Ideally possibility of writing hidden drafts and preview

Also I will implement a Gallery module that should have at least following features:
- HTML5 Multi-Upload-Support and ideally batch-resizing of Pictures
- Display gallery as grid with fancy zooming
- Drag&Drop reordering of pictures
And depending on the required time investment I would also add:
- Gallery Settings: Allowing some display options such as thumbnail size, picture descriptions, pre-loading of images, image zoom type, maybe watermark
- Different gallery display types: classic gallery, image slider, etc.

So altogether its going to be an exciting winter!

Yesterday I stumbled upon a whole range of software I didn't know it exists. I've found Netsparker, that can automatically scan a website for vulnerabilities such as SQL Injection and Cross Site Scripting threats. All it needs is the URL to your website and it searches and exploits every possible interaction with server side scripts.

There is a Community Edition of Netsparker, which is free but has limited features. Nonetheless it helped me find *a lot* of SQL Injection and XSS threats on my websites. If you run any type of non-static website, I'd strongly suggest to try out this tool. I am damn glad to have used it.

You might also want to check out the comparison of 60 similar tools in this area.

My project was mostly complete by the time I posted my previous report, so during last week I concentrated on fixing bugs.

Things done this week:

• I fixed the tracker functionality to work correctly with Drizzle. The only problem was that Drizzle has no SET type, so I had to emulate it with binary flags and an INT column. After making these changes to the PMA_Tracker class everything started working,
• Advisor available on server’s Status tab works correctly with Drizzle, I had to add a few exceptions so that rules dependent on variables unavailable in Drizzle don’t fire,
• bug fixes and some JavaScript optimizations.

 

What I made this week:

This week I added handling for datetime-related data in grid editing and also fixed some bugs in grid editing. I think the grid editing feature is now complete and also the other features that I initially proposed to do in the context of GSoC 2011. All the new features have been merge to the official master repository and may be tested in here.

Things done this week:

• Added datetime picker in grid editing for datetime-related data type
• Replaced js/jquery/timepicker.js by Martin Milesich with timepicker by Trent Richardson, as suggested by Martin himself
• More handling for HTML entities escaping
• Fix some bugs in grid editing feature

I’m really curious to see the new features from me and other GSoC-ers tested by other phpMyAdmin devs & users and also to hear any feedback from them.

This is the final week of gsoc 2011. As I mentioned in last weeks report I had to continue with rewriting the querywindow.js functions using jquey this week.

Exactly 5 years ago, I posted a 'First Post' on this blog. Back then I was wondering how long this blog would survive. Apparently it still exists. Going over a few posts of the past 5 years I noticed there were some active periods and some slower ones. Times were I posted things that I saw on the streets or read in the newspaper, but I think my blog has evolved into a space were I share IT and technology related stuff that I discover, am working on or I shouldn't forget.
By the way, the top 3 of most visited posts over the last 5 years are IT related :

1. Two-way MySQL replication
2. Rename multiple tables in MySQL database
   
3. Gadget Keyboard

BTW : A top 5 of the most popular post of the last 30 days is in the column on the right.

According to the schedule I had to continue with ajaxify the table maintenance options in this week. Last week I did some modifications with this task and there were some bugs with that. Marc showed me that some important information are missing with the results of ajaxified table maintenance actions. In CHECK TABLE action there was a table which contains Msg_type and Msg_text information in non ajax configuration but in ajax configuration it was not there. In order to make this information available I had to do the following changes.

This week, I finished “grid editing” feature and restructured code in makegrid.js file. These changes were already merged into the official master branch and can be tested in the demo page of phpMyAdmin.

Things done this week:

• Finish grid editing feature
  I added grid editing hint when hovering “Edit” link in table’s rows, alert when user edit some field in non-unique table (i.e., table with no primary key), fix some bugs.
• Remove inline edit feature
• Restructure code in makegrid.js
• Add configuration for maximum number of records stored in pma_table_uiprefs
  I added code in Table.class.php to check the number of records and delete older records in pma_table_uiprefs when saving/updating a record in the table.

Things to do next week:

• More bug fixing, documentation and code cleaning
• Improve grid editing: add more specific editor for certain data type (e.g., datetimepicker for DATETIME data type)

With the end of 12th week of GSoC 2011, I and other GSoC-ers are approaching the end of official coding time. For me, all the planned things are done, except for one thing: edit only selected field (see Project Detail section in my proposal). I think this feature won’t be needed anymore, since we can combine “show/hide column” and “grid editing” feature to achieve this. Hopefully there is nothing else missing from my project in the context of GSoC 2011.

Although the GSoC 2011 will end soon and I have already graduated from my college (which for me means: time to go to work), it doesn’t mean that I will stop my contribution for phpMyAdmin. I will still hang around in the mailing list and put my contributions for phpMyAdmin.

My Project is completed. The only thing that is left to do is to improve the code style, write some documentation on the phpMyAdmin wiki, fix any occurring bugs and tweak some things here and there.

As our GSoC students are approaching quite well, we've already numerous features included in current master, which are worth mentioning. You can try all bellow mentioned features on our demo server.

Grid editing provides really simple way of editing data, by simply clicking on it while browsing table. Just try it on some table.

Performance suggestions are part of completely reworked server status and can give you valuable information how to tune your server. You can see it on demo server.

Another nice addition to server status page is live monitor, which charts basic server information in real time. Again, try it on demo server (you need to press start for now, this will probably go away soon).

Other big, thought not that fancy change is complete support for routines. This includes stored procedures/functions, triggers and events. For example see routines in sakilla database.

Of course there is much more to mention, like improving of AJAX in lot of places, GIS support.

On the other side, we've also recently decided to remove support for Microsoft Excel import and export as used PHPExcel library seems to suffer some licensing issues, which prevented phpMyAdmin from being included in Fedora. You can still use CSV or OpenDocument formats though.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

As our GSoC students are approaching quite well, we've already numerous features included in current master, which are worth mentioning. You can try all bellow mentioned features on our demo server.

Grid editing provides really simple way of editing data, by simply clicking on it while browsing table. Just try it on some table.

Performance suggestions are part of completely reworked server status and can give you valuable information how to tune your server. You can see it on demo server.

Another nice addition to server status page is live monitor, which charts basic server information in real time. Again, try it on demo server (you need to press start for now, this will probably go away soon).

Other big, thought not that fancy change is complete support for routines. This includes stored procedures/functions, triggers and events. For example see routines in sakilla database.

Of course there is much more to mention, like improving of AJAX in lot of places, GIS support.

On the other side, we've also recently decided to remove support for Microsoft Excel import and export as used PHPExcel library seems to suffer some licensing issues, which prevented phpMyAdmin from being included in Fedora. You can still use CSV or OpenDocument formats though.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

This week I have been coding hard on the Advisor system that I planned for a long time. It uses the mysqltuner 2.0 config as a base, though I have added much more information about each rule/recommendation.

According to the schedule I had to continue with ajaxifying table operations task this week.

This week I was working in grid editing feature. I spent a lot of time in writing code to update the where_clause for links in Actions column. It’s in a good progress and hopefully can be done in this week.

Things done this week:

• Fixed grid editing feature to update where_clause in Actions column (currently works for a table which do not have “update on changes” field)
• Added configuration to show/hide hint
• Fixed bug in “recent tables” feature (previously failed on table name or db name containing ‘.’ character)

Things to do next week:

• Fix more bug when updating where_clause for grid editing feature
• Remove inline edit feature

During this week I worked on Database Synchronize feature. At first, I tested it with my MySQL server and found out that it suffered a lot from latest theme changes because it was using some Status page CSS classes. After fixing it and refactoring source and target table lists to actually be in one table, not in two placed next to each other, I followed to make necessary changes for it to work with Drizzle. Fortunately for me, it worked right away so I just disallowed connections with servers that use different protocol than the loaded database interface can, and added a few variables that can differentiate between regular MySQL and Drizzle in case any problems arise in the future.

This week I am going to a week-long vacation, and when I return I will have a week left to find and fix remaining bugs and maybe look whether Drizzle replication can be somehow supported.

I wanted to check the consistency of the data partition on one of my servers. It is 6.5TB and formatted with XFS, so I ran :

#xfs_check /dev/sdb1

And I got :

xfs_check: out of memory

After some searching, it turns out that a lot of memory is needed to perform the xfs_check on a large file system : >6GB and you need to run it on 64bit, to able to address that memory.

My system is a 32-bit with only 4GB, so I would probably not be able to run xfs_check on my system, but there is another way :

#xfs_repair -n /dev/sdb1

This tools tries to repair a XFS filesystem, but with the -n switch no changes are written to the file system, so the effect is quite the same. It still uses a lot of memory if you have a lot of files/inodes on the file system, but 3GB on a 32-bit system should be sufficient.

Of course, if xfs_repair finds a problem, you can still run it without the -n switch, to repair the filesystem.

According to my timeline, this week I had to work with ajaxify the options in table operations. Mainly this week I focused on ajaxify two option in the table options. Those options are

Grid editing get a lot of improvements this week. After some discussion in the mailing list with my mentor, we agree on removing the edit mode and use “click to edit” instead. I also found the user experience is better than before. In this week, not all the planned “to do”s were completed. I will try to finish those things next week.

Things done this week:

• Removed “edit mode” and use “click to edit”
• Added grid editing support for SET, ENUM, and TEXT data type
• Added a configuration to save all edited fields at once
• Fixed some bugs in grid editing that also appears in inline edit

Things to do next week:

• Fix more bugs in grid edit
• add configuration to turn on/off hint (as suggested by Tyron)
• refactor code in js/makegrid.js, to make it cleaner and easier to read