it'll be more simple if we can store data on special cosocket object.

for example:

local ok, err = sock:set_bound_data(key, value)
local value, err = sock:fetch_bound_data(key)

then we can store k-v like this:

key: prepare_sql
value: statement_id

-- inside db:prepare(prepare_sql)

local statement_id = self.sock:fetch_bound_data(prepare_sql)
if statement_id then
    return statement_id
end

... -- do prepare as current 

self.sock:set_bound_data(prepare_sql, statement_id)
return statement_id

@agentzh how about we take # attach arbitrary data to cosocket instances to ngx_lua_module?

Hello when will this be official release?

Would love to know whether this one seems likely to get merged.

This will definitely get merged at some point since this PR was the result of my request to @membphis :) He's been doing me a favor.

Is there anything preventing this to merge? It would be cool to see it merged soon.

Just for the record, we'll redo this atop a new OpenResty builtin API for better performance. We already use the new way to add preparing statement support for PostgreSQL.

hello, when is added to the built-in function of this feature??

Are there any plans to complete this feature?

hello, are there any plans to complete this feature?

Just for the record, we'll redo this atop a new OpenResty builtin API for better performance. We already use the new way to add preparing statement support for PostgreSQL.

Really look forward the PREPARE statement support for MySQL. : )