Hi Piotr,

Yes, it is blocking currently. That will be fixed, I've been working
on the upstream version, just not ready yet.
ngx_drizzle and ngx_postgres weren't around at the time we started
development (I'm looking at ways to build on them if possible since
they do now exist).
We aren't really focused on providing a REST interface to the data, so
for our use case, this is exactly what was needed. Your mileage may
vary of course.

Brian

2010/7/22 Piotr Sikora <piotr.sikora@frickle.com>:
> Hi,
> I don't want to belittle your project, but it seems that:
> 1) you've re-implemented things already covered by ngx_drizzle (drizzle,
> mysql, sqlite) and ngx_postgres (postgresql),
> 2) you did this in the *blocking* way, which doesn't play nice with nginx,
> 3) you're exposing whole database to the public and require client-side
> scripts to have credentials to the database.
>
> It's great that you're also supporting MS SQL Server (via FreeTDS), but
> doing this in such fashion isn't going to help anyone. Imagine the case in
> which n users (where n >= worker_processes) would issue "SELECT
> sleep(2592000)" command. This would lock dbrelay for a month...
>
> Best regards,
> Piotr Sikora < piotr.sikora@frickle.com >
>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx