>>>>> "Bob" == Bob Kline <bkline@stripped> writes:
Bob> On Tue, 21 Sep 1999, Martin Ramsch wrote:
>> Obviously the root of the problem (or call it bug) is, that the field
>> i1 is defined to have a display width of only 1 character, but the
>> values 10 and 100 don't fit this display width. I don't know, what
>> the "standard" behaviour than should be ...?
Bob> Well, I'm not sure that's a meaningful question, since the variation
Bob> INT(n) is a MySQL extension to the standard.
hi!
Actually INT(display_size) is standard of all ODBC compliant SQL
servers.
Regards,
Monty
| Thread |
|---|
| • join + group by + concat(INT,...) Problem! (3.22.26a) | Andrew Shirrayev | 21 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Benjamin Pflugmann | 21 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Martin Ramsch | 21 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Bob Kline | 21 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Michael Widenius | 22 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Bob Kline | 22 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Benjamin Pflugmann | 21 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Martin Ramsch | 21 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Michael Widenius | 22 Sep |
| • Re: join + group by + concat(INT,...) Problem! (3.22.26a) | Andrew Shirrayev | 21 Sep |