Hi, one reason may be that you altered your table tooooooo often with alter table add / alter table drop. This may happen in case of application development, I know. As with normal alter table drop only the description of the table is changed and the data remains unchanged, the old, 'dropped' columns remain even in the description as invisible columns to describe the used, but not selectable part of the records. In case of millions of records this is the only chance to finish the alter table within a short time. And no distinction is made if there are many or few/none records in the table. The behaviour is the same. And after x alter tables there are few columns visible, but many columns stored in the description and the only help is alter table with the option RELEASE SPACE or an alter table modify causing the table to be restructured, for example if a varchar-column of definition length <= 254 (127 in case of UNICODE) is changed to one with a higher maximum length or vice versa or making 1-n column(s) the primary key or the like or rename table and create table <old_name> as select * from <new_name>, thus making the stuff explicit. Then do not forget privileges, views, triggers, indexes for the new table with the old name. (I prefer one of the alter tables because of all that stuff.)
Good luck Elke SAP Labs Berlin Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. > -----Original Message----- > From: Chris Jölly [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 22. März 2007 18:40 > To: maxdb@lists.mysql.com > Subject: General error;-1002 POS(1) Too many columns > > Hello! > > i have a small table with one pk integer column and 4 varchar columns > and want to issue the following alter statement to add a new column: > > alter table my_table add ("delete_record" smallint) > > if the table both is filled or empty i can not add the > column. i always > get the error message: > > > ---- Error ------------------------------- > Auto Commit: On, SQL Mode: Internal, Isolation Level: Not Committed > General error;-1002 POS(1) Too many columns > alter table my_table add ( "delete_record" smallint ) > > whats wrong with that statement? > > thx, chris > > -- > the version of the database is 7.5 running at suse linux... > > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
