Quick: Yeah, it was easy to make, since you had done all the hard work Sebastian :-)
Step 1: Search and replace (pg|postgres) with mysql Step 2: https://github.com/jhthorsen/mojo-mysql/commit/f67f48c4b97176275e50b52b66355338f0c70f9d Step 3: https://github.com/jhthorsen/mojo-mysql/commit/9a5fbc619a20ad5db25cdbced7c4f852a6be21de About step #3. I'm not sure if what I'm doing there is a hack or not. Any MySQL people out there that can comment on this? The fix to make UTF8 work is to both set the "mysql_enable_utf8" and make sure the table has "COLLATE = utf8_bin". Is the way to store/read UTF8 from MySQL? I suggest others to follow the same steps, if it's possible for other DBD drivers. It's nice to have the same API - especially when the API makes sense. I was looking at SQLite, but couldn't find any async support. I'm a bit surprised, since it's a file on disk... (Let's open a new thread if someone wants to make discuss this further) On Saturday, October 11, 2014 10:49:42 PM UTC+2, sri wrote: > > Today I release Mojo::mysql, a fork of Sebastian's Mojo::Pg which allow >> you to use the same API, but against the MySQL database. >> >> https://metacpan.org/release/JHTHORSEN/Mojo-mysql-0.01 >> > > Yay, that was quick! > > >> I'm also unsure if I will add migration support to Mojo::mysql, even if >> Mojo::Pg gets migrations support. I will however (most probably) accept >> pull requests for this feature. >> > > Yea, i think you're better off not implementing migrations, MySQL lacks > support for transactional ddl, which is what makes migrations for > PostgreSQL so awesome. Yesterday i was still a bit unsure if migrations are > going to stay in Mojo::Pg, but the ability to have your database schema > sync automatically and safely on startup is just too good. So they will say. > > -- > sebastian > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
