Re: DBI converting hex values

[samtregar]

If you can't convince DBI to leave your hex value alone you can always convert it back:

  $a = "Paul";
  $a =~ s!(.)!sprintf("%02x", ord($1))!eg;
  print "0x$a";

I'm sure there's a more clever way to do that with unpack, but I'm way too lazy to figure it out!

-sam

[shmem]

From Saints in our Book: "..and remember there are a lot of things monks are supposed to be but lazy is not one of them" :-)

perl -le ' print "0x",unpack "H*",pack "A*","Paul"'
0x5061756c

--shmem

[tye]

You might want to be more lazy and skip the pack "A*". (:

[shmem]

Darn, you're right... do { print ((my $hubris = $hubris) >>= 1)} for $this_one :-)

--shmem

[Sprad]

The problem, though, is that this DBI call is part of a larger module that encapsulates DB access for some tools. It's another layer on top of DBI. My layer doesn't know which items were formerly hex and which were strings all along, so I can't blindly convert.

I could convert, though, if there were a way to know what data I was getting back. That might be another way to tackle the problem, but I'm not sure how to do that either. All I've done so far is just hand back the result array, which works great for everything except these fields.