On 10/24/07 11:59 AM, Peter Karman wrote: > True. Although AFAIK, sqlite actually stores everything but the PK as a char > string and ignores the data type. So if you had an autoincrementing column > that wasn't the PK, it wouldn't strictly be an integer but it would be serial.
RDBO's "serial" column type is for serial integers only. I'm not sure what a "serial character" column would be, heh :) >> Anyway, I can't decide if this is a bug or not. You tell me :) What's more >> appropriate for the loader to produce for an "integer auto-increment" db >> column definition? An "integer" column that behaves auto-increment-y (the >> current behavior) or a "serial" column that also behaves that way? > > I would prefer 'serial' so that the distinction can be mapped more granularly > to a RHTMLO Field type. For example, the working column-to-field map I have > now maps the 'serial' type to 'hidden' fields, while 'integer' maps to > 'integer' fields. [Whether serial values should be hidden in a form is, of > course, a matter of opinion, which is why the map will be configurable.] Gotcha. Seems reasonable. > On a related note, would you be willing to consider a Float RHTMLO field > class? I have one somewhere I can send, or I can release it in the > Rose::HTMLx:: namespace as well. Sure, but why doesn't this suffice? http://search.cpan.org/dist/Rose-HTML-Objects/lib/Rose/HTML/Form/Field/Numer ic.pm -John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
