[development] Bug in _db_create_field_sql?
remorse at partners.org
Tue Feb 5 14:26:05 UTC 2008
I couldn't believe that there wasn't already a bug filed -- my email
was to see if I was missing something. I'm going to go file a bug now...
On Feb 4, 2008, at 7:49 PM, mark burdett wrote:
> Did you file a bug on drupal.org?
> When testing out precision 5 and scale 2, on the admin/build/
> modules page I got
> "user warning: For float(M,D), double(M,D) or decimal(M,D), M must
> be >= D"
> and the table is not even created (it's more of an error than a
> On Feb 4, 2008 2:37 PM, Richard Morse <remorse at partners.org> wrote:
>> Hi! I've discovered a possible bug in _db_create_field_sql for MySQL,
>> but I'm not positive, and I can't believe this hasn't come up before,
>> but I can't find any bug reports, so I'm wondering if there's
>> something I'm missing.
>> According to the MySQL docs, a numeric column specification is
>> (precision, scale) [at least, I think that's what they want -- they
>> talk about precision and scale in the data type reference, but refer
>> to length and decimals in the CREATE TABLE syntax]. However, in
>> _db_create_field_sql for MySQL, according to api.drupal.org, the
>> order used is scale, precision.
>> Is there something I'm missing? Is there already a bug report for
>> this, and if so where (and how did you find it)? I couldn't find
>> anything about this using either Google or Drupal search...
>> The information transmitted in this electronic communication is
>> intended only
>> for the person or entity to whom it is addressed and may contain
>> and/or privileged material. Any review, retransmission,
>> dissemination or other
>> use of or taking of any action in reliance upon this information
>> by persons or
>> entities other than the intended recipient is prohibited. If you
>> received this
>> information in error, please contact the Compliance HelpLine at
>> 800-856-1983 and
>> properly dispose of this information.
More information about the development