• Twig has been updated to 1.6.0 (which fixes a bug when using Assetic in the
  production environment);

• Doctrine has been updated to their latest minor versions;

• And as always, some minor bugs has been fixed.

The CHANGELOG
has all the details about the changes done in this release and you can also
have a look at the full
diff.

If you are starting a new project, you can get the Symfony Standard Edition
distribution on the download page.

If you already have a project based on the Symfony Standard Edition 2.0.x, you
can easily upgrade to 2.0.10 by getting the new
deps and
deps.lock
files.

Then, run the vendors script (it also clears your cache):

$ ./bin/vendors install

Remember that the Symfony2 Components are also available as standalone
libraries. You can get them via their dedicated read-only repositories on
Github (https://github.com/symfony/Finder for instance), install them via
PEAR (pear install symfony2/Finder), or even
install them via Composer.

Development mailing list

• A note on PR reviews
• Doctrine/entityManager memory leaks

Symfony2 development highlights

Master branch:

• a676598, 57cc531:
  [Form] added class LazyChoiceList
• 307f17d:
  [FrameworkBundle] code factorization in TraceableEventDispatcher

• 5aa5987:
  [Form] fixed form children are always validated in group Default

• dbd3a1b:
  [Security] allowed unsetting parentAcl on MutableAclInterface
• 1678a3d:
  [Validator] fixed Validator::validateValue() propagates empty validation root instead of the provided value

• 1dd302c:
  [Validator] fixed ConstraintViolationList::__toString() to not include dots in the output if the root is empty

• f904a9e:
  [Validator] fixed GraphWalker does not add constraint violation if error message is empty
• a103c28:
  [Validator] the Collection constraint adds ‘missing’ and ‘extra’ errors to the individual fields now

• de253dd:
  [Form] added read_only and disabled attributes

• fe85bbd:
  [Validator] simplified ExecutionContext::addViolation() and added ExecutionContext::addViolationAt()
• a30a679:
  [Validator] made ExecutionContext immutable and introduced new class GlobalExecutionContext

• 9153f0e:
  [Validator] deprecated ConstraintValidator methods setMessage(), getMessageTemplate() and getMessageParameters()

• 3c28ab7, c373d5b:
  [Routing] no prefix is required to override imported RouteCollections
• e9b4c58:
  [Console] enable process isolantion in shell
• 7cecb4e:
  [Form] added support for parent of FormBuilder
• 2e4ebe4:
  [Validator] renamed methods addViolationAtRelativePath() and getAbsolutePropertyPath() in ExecutionContext
• 7837f50:
  [Form] added FormUtil::singularify()
• 49d1464:
  [Form] implemented MergeCollectionListener which calls addXxx() and removeXxx() in your model if found
• 9b0245b:
  [Form] made prefix of adder and remover method configurable
• 9a4e22e:
  [Form] disallowed infinity in NumberToLocalizedStringTransformer
• d208f4e:
  [Form] made it possible to use models with only either addXxx() or removeXxx()
• b393774:
  [Form] used direct method access in MergeCollectionListener instead of Reflection to avoid problems when using class hierarchies
• 02f61ad:
  [Form] renamed choice and collection options ‘adder_prefix’ and ‘remover_prefix’ to ‘add_method’ and ‘remove_method’ and allowed to specify full method names
• 8dc40e4, 4847d3a:
  [FrameworkBundle] added config:dump-reference console command
• 58939f1, 9757958, 2f8ad93, fa32885:
  added configuration docs for TwigBundle (reverted)
• bd461e2:
  [Form] forms now don’t create empty objects anymore if they are completely empty and not required. The empty data for these forms is null
• 0753cee:
  [Form] fixed read_only attribute for expanded fields

2.0.x branch:

• a1b6d4c:
  [DependencyInjection] added a failing testcase for escaped % in array parameters
• 048fc2f:
  [Form] fixed broken MoneyType test for JPY
• 8e13095, a7b48c0:
  [DependencyInjection] fixed the unescaping of parameters to handle arrays

Repository summary: 3,869 watchers (#1 in PHP, #28 overall) and 1000 forks (#1 in PHP, #11 overall).

Updated plugins

• apostrophe:
  • fixed bug that caused page forms not to work
  • refactored getEmbedCode() so it doesn’t instantiate embed services twice and doesn’t crash if the service URL is bogus and the width and height aren’t known
  • don’t cache non-200 OK responses, it leads to SEO problems
  • refactored nonrecursive version of aFiles::rmRf
• apostropheBlog:
  • fix for XSS attack

They talked about us

• symfony range filter
• Silex: getting your project structure right
• Doctrine Sluggable and Transliteration
• Créez votre propre framework … avec les composants Symfony2 (partie 10)
• Silex and MongoDB simply
• Loading Yaml Fixtures in Symfony2 and Doctrine2
• Une semaine symfonique #265 – du 23 au 29 janvier 2012
• Servicios REST usando Silex micro-framework 2/2
• Créez votre propre framework … avec les composants Symfony2 (partie 11)
• Silex: set up your project for testing with PHPUnit
• Security – symfony 2 Tutorial – webdev’s Blog
• symfony??????
• Symfony Plugin #1: Act As Sortable
• Dynamic embedded forms in symfony
• Reset database before phpunit tests in Symfony2
• Symfony 1.4 Doctrine 1.2 MS SQL Server
• Symfony 2 auf dem Mac einrichten
• [symfony] HTML?????????????????????
• Symfony2 ExtJS generator – Uigen – (1. update) – type recognition
• How to reduce admin generator query in Symfony 1.4
• Symfony build model error: Unable to return affix for unknown CreoleType
• Login en Symfony sin usar sfGuardPlugin
• Form choice filter auto sort by name
• symfony??????-symfony???????
• Autenticazione con Facebook in applicazioni Symfony
• Symfony including extra libraries or classes
• Symfony 2 vs Code Igniter
• PHP????? -> Symfony????????????????

Let’s take a table with data as example, column c1 on table t2 references column c1 on table t1 – both columns have identical set of rows for simplicity.

CREATE TABLE `t1` (
`t1_c1` int(10) unsigned NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`t1_c1`)
) ENGINE=InnoDB;

CREATE TABLE `t2` (
`t2_c1` int(10) unsigned NOT NULL,
PRIMARY KEY (`t2_c1`),
CONSTRAINT `t2_ibfk_1` FOREIGN KEY (`t2_c1`) REFERENCES `t1` (`t1_c1`) ON UPDATE CASCADE
) ENGINE=InnoDB;

[revin@forge rsandbox_5_5_17]$ for int in {1..2000}; do ./master/use test -e "insert into t1 values($int)"; done
[revin@forge rsandbox_5_5_17]$ ./master/use test -e "insert into t2 select * from t1"

master [localhost] {msandbox} (test) > SELECT COUNT(*) FROM t1;
+----------+
| COUNT(*) |
+----------+
| 2000 |
+----------+
1 row in set (0.00 sec)

master [localhost] {msandbox} (test) > SELECT COUNT(*) FROM t2;
+----------+
| COUNT(*) |
+----------+
| 2000 |
+----------+
1 row in set (0.00 sec)

An expected behavior for DELETE IGNORE is that if the statement fails to delete all rows, none should be deleted at all, after all this is InnoDB right? Wrong, take a look at bug 44987. As stated on the bug, only 5.0 exhibits the above mentioned behavior on 5.1 and 5.5, MySQL will stop deleting rows if it encounters constraint errors.

To demonstrate on 5.5.17:

I delete some rows from t2 so some rows on t1 does not have a constraint.

master [localhost] {msandbox} (test) > DELETE FROM t2 WHERE t2_c1 BETWEEN 201 AND 400;
Query OK, 200 rows affected (0.00 sec)

Now I try to DELETE IGNORE rows 301 to 500 on t1, note rows 301 to 400 does not have any existing constraints from t2 as we deleted them from above.

master [localhost] {msandbox} (test) > DELETE IGNORE FROM t1 WHERE t1_c1 BETWEEN 301 AND 500;
Query OK, 100 rows affected, 1 warning (0.00 sec)

master [localhost] {msandbox} (test) > SHOW WARNINGS \G
*************************** 1. row ***************************
  Level: Error
   Code: 1451
Message: Cannot delete or update a parent row: a foreign key constraint fails (`test`.`t2`, CONSTRAINT `t2_ibfk_1` FOREIGN KEY (`t2_c1`) REFERENCES `t1` (`t1_c1`) ON UPDATE CASCADE)
1 row in set (0.00 sec)

As expected a warning is generated because rows 201 to 300 on t1 still has referencing foreign keys from t2. However, 100 has been deleted! Let’s see.

master [localhost] {msandbox} (test) > SELECT COUNT(*) FROM t1;
+----------+
| COUNT(*) |
+----------+
|     1900 |
+----------+
1 row in set (0.00 sec)

Now let’s check the slave.

[revin@forge rsandbox_5_5_17]$ ./node1/use test
...
slave1 [localhost] {msandbox} (test) > SELECT COUNT(*) FROM t1;
+----------+
| COUNT(*) |
+----------+
|     2000 |
+----------+
1 row in set (0.00 sec)

Uh oh, now the slave is out of sync, because the statement failed to delete all intended rows it was not written to the binary log and consequently not reaching the slave.

So how can you workaround this? Simple, 1) do not use IGNORE, be critical about your data 2) use ROW* based replication. When using the latter, MySQL will log separate statements for each row that is deleted – so if the first 100 rows was successfully deleted then those 100 events are logged and eventually replicated.

[revin@forge rsandbox_5_5_170]$ ./master/use test
...
master [localhost] {msandbox} (test) > SELECT @@binlog_format;
+-----------------+
| @@binlog_format |
+-----------------+
| ROW             |
+-----------------+
1 row in set (0.00 sec)

master [localhost] {msandbox} (test) > DELETE FROM t2 WHERE t2_c1 BETWEEN 201 AND 400;
Query OK, 200 rows affected (0.00 sec)

master [localhost] {msandbox} (test) > DELETE IGNORE FROM t1 WHERE t1_c1 BETWEEN 301 AND 500;
Query OK, 100 rows affected, 1 warning (0.01 sec)

master [localhost] {msandbox} (test) > SELECT COUNT(*) FROM t1;
+----------+
| COUNT(*) |
+----------+
|     1900 |
+----------+
1 row in set (0.00 sec)

[revin@forge rsandbox_5_5_170]$ ./node1/use test
...
slave1 [localhost] {msandbox} (test) > SELECT COUNT(*) FROM t1;
+----------+
| COUNT(*) |
+----------+
|     1900 |
+----------+
1 row in set (0.00 sec)

* MIXED mode will not work since the query in this example will be considered STATEMENT (http://dev.mysql.com/doc/refman/5.1/en/binary-log-mixed.html) thus failure to execute the query successfully means it will not get logged.

So how are you supposed to check for corruption that might be introduced by bad hardware, a bug, or so forth?

It’s a great question. The answer I would give for most cases is “check your backups for corruption instead of your live server.” You need to do this anyway — a backup that isn’t checked is a ticking time bomb. You need to verify (at least periodically) that your backups are recoverable.

The usual procedure goes like this: copy your backup somewhere, start a server instance on it, and run CHECK TABLES. You can use the mysqlcheck program to do this conveniently.

You could also use innochecksum, which doesn’t require starting the server. But it only verifies that each page’s checksum matches the page’s data, it doesn’t do all the other checks that are built into InnoDB (making sure that the LSNs are sane, for example).

How often? As often as possible. Some people refresh their dev/staging environment every day with last night’s backup, which is a great way to make failures obvious, as long as you verify that it truly does happen (e.g. what if it fails and you keep running with yesterday’s without knowing it?). If you can’t do it daily, then weekly is perfectly acceptable to most people. I’m not saying a specific interval should/ought to be your goal, I’m just remarking on what a lot of people seem to feel good about.

Todays installment continues the Chapter about efficiently fetching partial results—that is, whenever you don’t need all the rows. Todays part explains how to fetch the next page efficiently.

Continue Reading

Development mailing list

• Call for volunteers for Netbeans Sf2 plugin development

Symfony2 development highlights

Master branch:

• 3b260d2:
  refactored the collector to separate the loggers per connection
• e37783f:
  [DoctrineBridge] refactored the query sanitization in the collector
• 2a998e0:
  [FrameworkBundle] handle disabled csrf protection in the PHP templating form helper
• 3a1699a:
  handle disabled csrf protection in the Twig FormExtension
• 87b16e7:
  [Form] greatly improved ChoiceListInterface and all of its implementations (EntityChoiceList was adapted, the methods getEntities(), getEntitiesByByKeys(), getIdentifier() and getIdentifierValues() were removed/made private. Instead of the first two you can use getChoices() and getChoicesByValues(), for the latter two no replacement exists. ArrayChoiceList was replaced by SimpleChoiceList. PaddedChoiceList, MonthChoiceList and TimezoneChoiceList were removed. Their functionality was merged into DateType, TimeType and TimezoneType)
• e1fc5a5:
  [Form] restricted form names to specific characters to fix generation of HTML IDs and to avoid problems with property paths
• f533ef0:
  [Form] added ChoiceView class for passing choice-related data to the view
• 43e0db5:
  [DomCrawler] add support for multivalued form fields
• 399af27:
  [Form] implemented checks to assert that values and indices generated in choice lists match their requirements
• ed9c348:
  [Security] Authentication(Success|Failure)Handler can now return null
• 2dd4bf1, c3f637b:
  [Form] support for PATCH method in forms
• d4300b9, b879397:
  [WebProfilerBundle] tweak the time view
• a52c675:
  [WebProfilerBundle] improved the logger panel

2.0.x branch:

• 7f96c8a:
  [HttpKernel] prevent php script execution in cached ESI pages using HttpCache
• c3f0ec7:
  [DoctrineBundle] made DoctrineBundle fowards compatible with Doctrine 2.2

Repository summary: 3,830 watchers (#1 in PHP, #27 overall) and 983 forks (#1 in PHP, #11 overall).

Updated plugins

• dcReloadedFormExtra:
  • added a uniquenes checker widget that checks the uniqueness of a value using an Ajax callback
• sfSyncContent:
  • created default parameters for sync content to be frontend dev FROM prod@production
• apostrophe:
  • added an app.yml option to return email links in a different format that allows apostrophe.unobfuscateEmailInline to be called outside of the a_js spool
  • all unlink() and rmdir() calls in the product now invoke aFiles::unlink() and aFiles::rmdir(), providing a capability to override these methods
  • the aFiles class has been refactored into a BaseaFiles? class and an empty aFiles subclass, allowing convenient overrides
  • a_button helper now accepts a single array of options as an alternative to the full list of parameters
  • slideshows are allowed to have the crossfade transition now even if they have no height specified
  • fixed event bug in menutoggle script and added jQuery 1.7 to the plugin
  • annotation of multiple media items works again
• apostropheBlog:
  • added a ‘first’ class to the first pager in the blog index

They talked about us

• deSymfony 2012 inicia su call for papers
• Create your own framework … on top of the Symfony2 Components (part 11)
• Une semaine symfonique #264 – du 16 au 22 janvier 2012
• symfony forward through LAN
• Use virtuals forms with Symfony2
• Create your own framework … on top of the Symfony2 Components (part 12)
• sqlite w ?rodowisku developerskim w symfony i symfony2
• Load fixtures with Symfony2 and YAML files
• Onde encontrar Bundles para o Symfony2
• Notes: Symfony 2 (?)
• Nazwa.pl, PostgreSQL i Symfony
• Recording ‘Last Activity’ for Users in Symfony2 + FOSUserBundle
• Get started with Symfony in Amazon Cloud
• symfony schema.yml ???
• Symfony YAML MySQL Workbench Plugin
• Symfony 1.4 Admin Generator – Aktuelles Objekt in Partial
• Uso de sfWidgetFormJQueryDate (datepicker) en Symfony
• Symfony meets APC (Alternative PHP Cache)
• ???? ?? ????? – ???????? ????????????????? ?????? ??? Symfony

We’ve gotten really good feedback on this tool, including this nice mention on Stack Exchange:

Percona just built a tool to do just that called the Configuration Wizard. I tested it out once just to see what it would return and the results were pretty darn close to what we were using on our servers, whose cnf’s were put together by highly trained mysql certified dba’s.

So what’s changed in the new version of the Configuration Wizard? Quite a few things. We’ve rolled out the first iteration of the account and profile features. Now you get a homepage with your configuration files, so you can manage them and return to them anytime you like.

From this page (click on the image for a fullsize view) you can do things like sharing configuration files and emailing them to yourself. The new release also adds features like downloading the configuration files so you don’t have to copy-paste them.

If you share a configuration file, then the URL can be loaded by anyone, even if they’re not logged in. It’s kind of like sending someone a link to a pastebin or something like that. Screenshot:

Another new feature is something I’ve wanted for a long time: the ability to generate a more strict, safer configuration file. There’s a new page in the Wizard that lets you set a lot of sanity/safety options to prevent common problems MySQL users run into because of too-permissive MySQL behaviors. These are the kinds of things that Drizzle fixes — and should be fixed by default in MySQL — but never will be because they might break applications that rely on the default behaviors. If you’re building an application from the ground up, now you can prevent bad things from getting a nose under the tent. Here’s a screenshot:

In addition to these things, we have added a number of other features you might not notice, which I won’t spend much time on — they’re things like an integrated feedback form at the left of the page and so on.

What’s next? Well, next I think we’re going to turn our attention to adding new tools, rather than improving this one. I have a list of tools that people have requested or suggested: a SQL formatter, a visual EXPLAIN tool, a configuration advisor, a query analysis tool, a way to register a server’s essential characteristics and then get advice when there’s a new release that might be beneficial for you, and so on. I have selected the next priorities, but I don’t want to spoil the surprise or promise something if it turns out to be harder than I think it will be. What ideas do you have? Let me know by leaving your feedback in the comments.

We hope this suite of free browser-based tools helps you become a more productive MySQL user and administrator!

With Oracle’s stock MySQL you cannot move your ibd files freely from one server to another or from one database to another. The reason is that the table definition is stored in the InnoDB shared tablespace (ibdata) and the transaction IDs and log sequence numbers that are stored in the tablespace files also differ between servers. Therefore our example will be very straightforward: we’ll delete some rows from a table in order to recover the table later.

Most of these limitations are solved on Percona Server . More info about this in the conclusion section of this post. This post will be focus on how to recover a single tablespace using stock MySQL server.

First, you must meet certain prerequisites to be able to restore a ibd tablespace:

• The ibd file must be from a consistent backup with all insert buffer entries merged and have no uncommitted transactions in order to not be dependent of the shared tablespace ibdata. That is, shutting down with innodb_fast_shutdown=0. We’ll use XtraBackup to avoid the server shutdown.
• You must not drop, truncate or alter the schema of the table after the backup has been taken.
• The variable innodb_file_per_table must be enabled.

Then, our first step is to get a consistent backup.

First we need to copy all the data to an output directory:

The –export option is the magic trick that will help us to get a consistent backup with complete independent ibd files without shutting down the service. In the second step the use of –export option runs a recovery process on the backup with innodb_fast_shutdown=0 and therefore merging all the insert buffers.

# innobackupex --defaults-file=/etc/my.cnf --export /tmp/

Then apply the logs to get a consistent backup:

# innobackupex --defaults-file=/etc/my.cnf --apply-log --export /tmp/2012-01-22_14-13-20/

Now we’re going to delete some data from one table. In this case we’re going to delete the salary information from the user 10008:

mysql> SELECT * FROM salaries WHERE emp_no=10008;
+--------+--------+------------+------------+
| emp_no | salary | from_date | to_date |
+--------+--------+------------+------------+
| 10008 | 46671 | 1998-03-11 | 1999-03-11 |
| 10008 | 48584 | 1999-03-11 | 2000-03-10 |
| 10008 | 52668 | 2000-03-10 | 2000-07-31 |
+--------+--------+------------+------------+

mysql> DELETE FROM salaries WHERE emp_no=10008;

The next step is where we are going to save a lot of time and some headaches Instead of recovering all the InnoDB data we are going to recover only the “salaries” table:

• Discard the tablespace of the salaries table:


mysql> set FOREIGN_KEY_CHECKS=0;
mysql> ALTER TABLE salaries DISCARD TABLESPACE;

• Copy the salaries.ibd files from the backup to the database data directory:

# cp /tmp/2012-01-22_14-13-20/employees/salaries.ibd /var/lib/mysql/data/employees/

• Import the new tablespace:


mysql> set FOREIGN_KEY_CHECKS=0;
mysql> ALTER TABLE salaries IMPORT TABLESPACE;
mysql> set FOREIGN_KEY_CHECKS=1;
mysql> SELECT * FROM salaries WHERE emp_no=10008;
+--------+--------+------------+------------+
| emp_no | salary | from_date | to_date |
+--------+--------+------------+------------+
| 10008 | 46671 | 1998-03-11 | 1999-03-11 |
| 10008 | 48584 | 1999-03-11 | 2000-03-10 |
| 10008 | 52668 | 2000-03-10 | 2000-07-31 |
+--------+--------+------------+------------+

The salary history from the user is back again!

Conclusion:

As we learned , you can also recover single InnoDB table as with MyISAM but knowing in advance that there are some prerequisites to comply.

Percona Server relaxes a lot of limitations and is able to import tables from different Server instance, when table was altered or truncated in the meanwhile. Though this only works if table was
“exported” with Xtrabackup as this exports essential information from main tablespace which is not stored in .ibd file. innodb_import_table_from_xtrabackup=1 should be enabled for such advanced import process to work. You can read more about this feature in Percona Server Documentation

In the next blog post I’ll explain how to do recovery using Percona Data Recovery toolkit.