why too long entries get _cut_ without error

2002-01-17 Thread Henning Sprang
Hy, I have an interesting question, I just realized that Mysql simply cuts Data i want to insert into a field when it is too long, without giving any warning or error message. Ok, i know now that this happens and that i have to take care myself that this doesn't happen. But i am very curious

Re: why too long entries get _cut_ without error

2002-01-17 Thread M. A. Alves
On Thu, 17 Jan 2002, Henning Sprang wrote: ... I just realized that Mysql simply cuts Data i want to insert into a field when it is too long, without giving any warning or error message. . . If the field has fixed length that is standard behaviour (together with right-padding too short

Re: why too long entries get _cut_ without error

2002-01-17 Thread Henning Sprang
M. A. Alves wrote: On Thu, 17 Jan 2002, Henning Sprang wrote: ... I just realized that Mysql simply cuts Data i want to insert into a field when it is too long, without giving any warning or error message. . . If the field has fixed length that is standard behaviour (together with

Re: why too long entries get _cut_ without error

2002-01-17 Thread M. A. Alves
On Thu, 17 Jan 2002, Henning Sprang wrote: ... I just realized that Mysql simply cuts Data i want to insert into a field when it is too long, without giving any warning or error message. . . If the field has fixed length that is standard behaviour (together with right-padding too short

Re: why too long entries get _cut_ without error

2002-01-17 Thread Henning Sprang
M. A. Alves wrote: On Thu, 17 Jan 2002, Henning Sprang wrote: So your field is of fixed length type (you hadn't told us that yet). Aehm, no, it isn't! It's VARCHAR. Sorry I overread that part, a colleague sitting next to me told me that this behaviour is _normal_ and documented, and so I

Re: why too long entries get _cut_ without error

2002-01-17 Thread M. A. Alves
On Thu, 17 Jan 2002, Henning Sprang wrote: So your field is of fixed length type (you hadn't told us that yet). Aehm, no, it isn't! It's VARCHAR. Doesn't matter: If you assign a value to a CHAR or VARCHAR column that exceeds the column's maximum length, the value is truncated to fit. (MySQL

Re: why too long entries get _cut_ without error

2002-01-17 Thread Ryan Fox
Doesn't matter: If you assign a value to a CHAR or VARCHAR column that exceeds the column's maximum length, the value is truncated to fit. ok, so it isn't depending on fixed length as you first said, and the reason for it is just the simple design of sql, right? As I see it, the question

RE: why too long entries get _cut_ without error

2002-01-17 Thread Carsten H. Pedersen
Doesn't matter: If you assign a value to a CHAR or VARCHAR column that exceeds the column's maximum length, the value is truncated to fit. ok, so it isn't depending on fixed length as you first said, and the reason for it is just the simple design of sql, right? As I see it, the

Re: why too long entries get _cut_ without error

2002-01-17 Thread M. A. Alves
On Thu, 17 Jan 2002, Henning Sprang wrote: ok, so it isn't depending on fixed length as you first said, and the reason for it is just the simple design of sql, right? Right. (Sorry for the previous inacuracy, I was using 'fixed' in a wide sense viz. including 'bounded'.) Cheers, -- , M

Re: why too long entries get _cut_ without error

2002-01-17 Thread M. A. Alves
On Thu, 17 Jan 2002, Ryan Fox wrote: The current action is that this value is truncated to fit the column. The other option would be to automagically expand the column's length so the value would fit. Despite what the original poster may think, they _really_ don't want that to happen.