Update gluesql

[serprex]

gluesql made all their methods async,
but even replacing Mutex with tokio's async Mutex doesn't solve borrowing issues, seems gluesql isn't tokio compatible, so execute with futures::executor::block_on

Fixes #127

[sunng87]

Thank you! I was trying to use async gluesql in our query APIs and failed. Since it's all memory based operation, it's ok to use blocked operation here.

[ever0de]

hello @sunng87 :)

I commented on the follow-up story.
gluesql/gluesql#1247 (comment)

The existing sync API was also implemented using block_on, so I think it's doing the same thing.

example of a cli workspace

Now that I checked the above, the problem is caused by gluesql not supporting Send.
The reason we only supported the async api was to make the block_on api optional when the sync api was needed at the user level.

Thanks for the great example!

[sunng87]

Hey @ever0de ! Thank you for the clarification. I think you have a plan to make gluesql Send, I will update the example when it happens