The error you get from the page has nothing directly to do with your SQL injection attempt. The site appears to employ a simple casting to ensure
id is numeric, so your query becomes a valid query which returns nothing unless you send in a plain number:
$id = (int)$_GET['id'];
In other words, not all queries you can mess up from the URL line are automatically fully SQL injectable.
The error you get is the one from the query returning nothing, because there are no rows with a type of zero.
This kind of "simple whitelisting" is just not exploitable, because the exploit will never reach the SQL layer; even if other parts of the web site might well be (the use of mysql_* functions and the lack of checks for query failure are not good signs).
However, I think it would be way better to look for some SQL injection testing website (I knew of one but it is now apparently offline, the domain for sale) and leave the good people of Montreuil-sur-Mer alone with their bonne adresses. In a pinch, there are several tutorials that you can deploy to a virtual machine to test the different approaches and the different SQL platforms.