Meaning of column_info field names

On Mar 20, 2006, at 3:04 PM, Paul DuBois wrote:
> Some member names to not begin with underscore, and
others do. The  
> ones that
> begin with underscore look to me to be values that are
MySQL-specific.
>
> Question: Is there some kind of Ruby DBI convention
that engine- 
> specific
> column metadata values should begin with underscore?  I
ask because  
> Mysql.rb
> seems to be about the only driver that provides
non-standard metadata
> fields.

Looks like there isn't really any convention. The DB2 DBD
appears,  
for example, to set the field "db2_type". Do you
think having a  
convention would be helpful?

Francis Hwang
http://fhwang.net/



_______________________________________________
Ruby-dbi-next mailing list
Ruby-dbi-nextrubyforge.org
h
ttp://rubyforge.org/mailman/listinfo/ruby-dbi-next

On 3/21/06 12:56, "Francis Hwang" <serafhwang.net> wrote:

> 
> On Mar 20, 2006, at 3:04 PM, Paul DuBois wrote:
>> Some member names to not begin with underscore, and
others do. The
>> ones that
>> begin with underscore look to me to be values that
are MySQL-specific.
>> 
>> Question: Is there some kind of Ruby DBI convention
that engine-
>> specific
>> column metadata values should begin with
underscore?  I ask because
>> Mysql.rb
>> seems to be about the only driver that provides
non-standard metadata
>> fields.
> 
> Looks like there isn't really any convention. The DB2
DBD appears,
> for example, to set the field "db2_type".
Do you think having a
> convention would be helpful?
> 
> Francis Hwang
> http://fhwang.net/

Well, as opposed to having no convention, yes, I think that
would be
preferable. 

Right now I don't think think we have much documentation
that asserts any
particular set of standard column_info members, or any
convention about how
to name non-standard column_info members.

How do we begin this process?


_______________________________________________
Ruby-dbi-next mailing list
Ruby-dbi-nextrubyforge.org
h
ttp://rubyforge.org/mailman/listinfo/ruby-dbi-next