Improving doc

Author: moufmouf

.gitignore

@@ -1 +1,2 @@
 vendor/
+composer.lock

README.md

@@ -56,14 +56,15 @@ Because it is **the most efficient way to deal with queries that can have a vari
 Think about a typical datagrid with a bunch of filter (for instance a list of products filtered by name, company, price, ...).
 If you have the very common idea to generate the SQL query using no PHP library, your code will look like this:
 
+###Without Magic-query
 <div class="alert"><strong>You should not do this!</strong></div>
 
 ```php
 // People usually write queries like this:
 $sql = "SELECT * FROM products p JOIN companies c ON p.company_id = c.id WHERE 1=1 ";
 // They keep testing for parameters, and concatenating strings....
 if (isset($params['name'])) {
-	$sql .= "AND p.name LIKE '".addslashes($params['name'])."%'";
+	$sql .= "AND (p.name LIKE '".addslashes($params['name'])."%' OR p.altname LIKE '".addslashes($params['name'])."%')";
 }
 if (isset($params['company'])) {
 	$sql .= "AND c.name LIKE '".addslashes($params['company'])."%'";
@@ -77,14 +78,26 @@ if (isset($params['country'])) {
 Concatenating SQL queries is **dangerous** (especially if you forget to protect parameters).
 You can always use parametrized SQL queries, but you will still have to concatenate the filters.
 
-To avoid concatenating strings, frameworks and libraries have used different strategies. Building a full ORM (like
+###With Magic-Query
+
+```php
+// One query with all parameters
+$sql = "SELECT * FROM products p JOIN companies c ON p.company_id = c.id WHERE 
+	(p.name LIKE :name OR p.altname LIKE :name)
+	AND c.name LIKE :company
+	AND c.country LIKE :country";
+
+$magicQuery = new MagicQuery();
+$sql = $magicQuery->build($sql, $params);
+```
+
+###Other alternatives
+
+To avoid concatenating strings, frameworks and libraries have used different strategies. Using a full ORM (like
 Doctrine or Propel) is a good idea, but it makes writing complex queries even more complex. Other frameworks like
 Zend are building queries using function calls. These are valid strategies, but you are no more typing SQL queries
 directly, and let's face it, it is always useful to use a query directly.
 
-This is where Magic-query becomes helpful.
-
-
 How does it work under the hood?
 --------------------------------
 
@@ -112,3 +125,10 @@ $conn = \Doctrine\DBAL\DriverManager::getConnection($connectionParams, $config);
 
 $magicQuery = new \Mouf\Database\MagicQuery($conn);
 ```
+
+Any problem?
+------------
+
+As we said, a lot happen to your SQL query. In particular, it is parsed using a modified version
+of the php-sql-parser library. If you face any issues with a complex query, it is likely there is a bug
+in the parser. Please open [an issue on Github](https://github.com/thecodingmachine/magic-query/issues) and we'll try to fix it.