On Saturday, February 25, 2017 at 8:05:43 PM UTC-8, John Backus wrote: > > Sharing this here after a brief discussion on the sequel issue tracker > <https://github.com/jeremyevans/sequel/issues/1293>. > > It can be very confusing to test code that involves blobs because it is > very unclear whether you have a bug or one of your values is secretly a > Sequel::SQL::Blob type. This ended up being a problem for me so many > times that I ended up adding this to my spec helper > > > class Sequel::SQL::Blob > def inspect > "#<#{Sequel::SQL::Blob} #{super}>" > endend > > and I view this as a usability bug which is why I'm reporting here and not > on the mailing list. I'll give an example below >
This was already changed earlier this month, along with all of the other types that inherit from core types. The commit for Sequel::SQL::Blob is https://github.com/jeremyevans/sequel/commit/22c7fe2e911aba67deac2880c073ad0f7a07eb53 This will be released on Wednesday in Sequel 4.44.0, per Sequel's usual monthly release schedule. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
