Another post convert to md

2 files changed, 21 insertions, 21 deletions

diff --git a/_posts/2008-06-21-debug-your-dbix-class-queries.md b/_posts/2008-06-21-debug-your-dbix-class-queries.md
new file mode 100644
index 0000000..dc58280
--- /dev/null
+++ b/_posts/2008-06-21-debug-your-dbix-class-queries.md
@@ -0,0 +1,21 @@
+---
+layout: post
+title: debug your DBIx::Class queries
+summary: In which I explain how to see SQL queries generated for DBIx::Class.
+---
+
+If you use DBIx::Class and want to see what the SQL generated looks like, you can set the environment variable **DBIC_TRACE**.
+
+```sh
+% DBIC_TRACE=1 my_programme.pl
+```
+
+And all the SQL will be printed on **STDERR**.
+
+If you give a filename to the variable, like this
+
+```sh
+% DBIC_TRACE="1=/tmp/sql.debug"
+```
+
+all the statements will be printed in this file.
diff --git a/_posts/2008-06-21-debug-your-dbix-class-queries.textile b/_posts/2008-06-21-debug-your-dbix-class-queries.textile
deleted file mode 100644
index 3d0d787..0000000
--- a/_posts/2008-06-21-debug-your-dbix-class-queries.textile
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: post
-category: perl
-title: debug your DBIx::Class queries
----
-
-If you use DBIx::Class and you want to see what the SQL generated looks like, you can set the environment variable DBIC_TRACE.
-
-{% highlight vim %}
-% DBIC_TRACE=1 my_programme.pl
-{% endhighlight %}
-
-And all the SQL will be printed on STDERR.
-
-If you give a filename to the variable, like this
-
-{% highlight vim %}
-% DBIC_TRACE="1=/tmp/sql.debug"
-{% endhighlight %}
-
-all the statements will be printed in this file.