{"?column?"=>"t"} behavior

Issue #133 duplicate
Stanislav Pankevich created an issue


If I write

select exists (select true from #{table} limit 1);

The result, pg gem gives to me, is {"?column?"=>"t"} or {"?column?"=>"f"}

Can I expect the form of such response format to be stable across different versions of pg gem, earlier and future as well?

Or maybe there is a better way of parsing the result of such query, thus the generality of result parsed is ensured?

My use-case is here: https://github.com/stanislaw/truncate-vs-count/blob/master/truncate-vs-count-on-postgres.rb#L128


Comments (2)

  1. Log in to comment