I am moving the following from a different thread into this dbi-users
one, where it is more relevant, since it is effectively a DBI v2
suggestion. Portions not relevant to DBI v2 have been snipped out.
While poop-group is cc'd, send all replies on this subject just to
dbi-users. -- Darren Duncan
At 8:24 PM +0000 7/21/05, Terrence Brannon wrote (on poop-group):
> At 7:05 AM -0400 7/19/05, John Siracusa wrote:
>>I use a module (Rose::DB) that parses and formats db-specific column values
for me: various kinds of dates, "SET"s, arrays, all the crazy db-specific
data types that are a pain to manually parse and then format.
Are sets and arrays useful types? I don't think so. The date
functionality you speak of might belong in DBI proper perhaps?
Very few DBI abstraction modules provide this feature, but IMO it's
essential.
Yes, and since it is essential it belongs at DBI level perhaps?
