SQL Relay Icon

User Ratings

★★★★★
★★★★
★★★
★★
0
0
0
1
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 2 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
Write a Review

User Reviews

  • wkirkpa
    1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Great idea, but running behind on protocol versions I think. Was able to get postgresql drop in working, but it loads version 8.1 protocols vs. the current 9.1. "psql" was able to do a CREATE and DROP a table through sqrl tho, but couldn't do a "show all;" (recieved an empty reply). The most current mysql 5.1 drop in ("for mysql versions 5.1 and higher") library just hangs, using version 5.5.35 of mysql. Tried lower versions of the drop in, and they hang too. Tried both the 'mysql' client itself and a couple "normal apps". A connection was being made to the sqrl daemon, and the debug logs suggest it was "happy", just the app(s) never got out of library startup. My goal was to map various mysql apps into postgres, hopefully leaving only one db to admin, on one server. So, the mysql drop in is the one I actually needed. Debugging a configuration can be more difficult than it might be. For example, you get just "can't connect to database" - which could mean anything from postgresql isn't even installed to a simple mistype of a password. There is alot of ground between those two extremes. A bit more clarity of the issue would be helpful. Lots of potential here.

    Posted 01/25/2014