From 7cc7aaf2823eb39a4d8f1d59c2105a0e1abf87bf Mon Sep 17 00:00:00 2001 From: Jakub Arnold Date: Tue, 31 Dec 2013 17:18:37 +0100 Subject: [PATCH] DAT GRAMMAR --- README.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.markdown b/README.markdown index f5406b21..d1be38da 100644 --- a/README.markdown +++ b/README.markdown @@ -70,7 +70,7 @@ If you have used JDBC before, you might have heard that prepared statements are to databases. This isn't exactly true all the time (as you can see on [this presentation](http://www.youtube.com/watch?v=kWOAHIpmLAI) by [@tenderlove](http://github.com/tenderlove)) and there is a memory cost in keeping prepared statements. -Prepared statements are tied to a connection, they are not database-wide, so, if you generate your queries dinamically +Prepared statements are tied to a connection, they are not database-wide, so, if you generate your queries dynamically all the time you might eventually blow up your connection memory and your database memory. Why?