Let me clarify three things: 1) I started on a MySQL backend a while ago, and didn't do much work on it. 2) Someone else (I won't point fingers, he can stand up himself if he chooses) is working on a MySQL backend. 3) Adding arbitrary backends is very easy, *except* for migration support. So it's within the realm of reason to create a HDBC-generic backend, sans migration support. In fact, the PostgreSQL backend is basically an HDBC backend already; if this is a feature people will actually use, let's do it. Michael On Tue, Apr 26, 2011 at 7:33 PM, Nikitiskiy Dmitriy <nick@bel.ru> wrote:
I vote for ODBC support with GenericSql. ODBC will allow many other databases support.
26.04.2011 19:02, Greg Weber wrote:
it doesn't compile. Perhaps a day's work to get it going. Postgresql and sqlite both use a GenericSql module that MySQL can also use. Either way, there are already example SQL backends. You are the first haskeller I have seen show interest in MySQL for a new project, which is the main reasons why that backend is bit-rotting.
On Tue, Apr 26, 2011 at 1:17 AM, Max Cantor <mxcantor@gmail.com <mailto:mxcantor@gmail.com>> wrote:
I've heard that there is a mysql backend in development for persistent. what is its current status? before you start telling me how postgres is better, let me say that I know it is. but, the AWS RDS implementation of MySQL is very compelling and kind of makes up for the differences..
_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel