New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

$Column->{UNSIGNED} seems to be forgotten #154

Open

rwfranks opened this issue Oct 27, 2024 · 0 comments

rwfranks commented Oct 27, 2024

Transcribed verbatim from CPAN RT#110105, warts and all.

Sat Dec 05 16:27:27 2015 porton [...] narod.ru - Ticket created
Subject: $Column->{UNSIGNED} seems to be forgotten

Date: Sat, 05 Dec 2015 23:27:01 +0200
To: [email protected]
From: Victor Porton [email protected]

It looks like that DBI.pm provides no way (except to to look into
INFORMATION_SCHEMA) to check if a given column of a table is UNSIGNED.

For me, it looks like that DBI developers just forgot about querying
UNSIGNED attribute.

I propose to add UNSIGNED or UNSIGNED_ATTRIBUTE to the hashes returned
by column_info(). It should be 0, 1, or undef (for non-numeric types).

--
Victor Porton - http://portonvictor.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment