create a temp table, copy all rows, drop original table, create new table
with new defs, and then copy all data back. So actually MSSql uses more
space to make table modifications. This is using Enterprise manager. You
could do it more efficiently with sql statements.
> -----Original Message-----
> From: Scott Stroz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 02, 2004 9:57 AM
> To: CF-Talk
> Subject: Re: Access alternatives (WAS: Security gurus out there?)
>
> Some of Micha's points are inaccurate...in some downtime, I plan on
> testing each issue he presents.
>
> I can tell you that the first point he makes is inaccurate. In
> version 4.0.17 you CANNOT 'define a varchar/char field
> 'auto_increment'. '
>
> That's about as far as I have gotten...I just started ;-)...but so far
> he is 0 for 1.
>
>
> ----- Original Message -----
> From: Mark A Kruger <[EMAIL PROTECTED]>
> Date: Thu, 2 Sep 2004 09:49:18 -0500
> Subject: RE: Access alternatives (WAS: Security gurus out there?)
> To: CF-Talk <[EMAIL PROTECTED]>
>
> Micha,
>
> Ok ok... so it has a few problems (lol). I think you should apply to
write
> the next "NOT MySQL for dummies" book.
>
> Seriously - this is a pretty comprehensive list and great fodder for
those
> of us who live off of upselling. Thanks!
>
> Mark A. Kruger, CFG, MSCE
> www.cfwebtools.com
> www.necfug.com
> http://blog.mxconsulting.com
>
>
> -----Original Message-----
> From: Micha Schopman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 02, 2004 9:02 AM
> To: CF-Talk
> Subject: RE: Access alternatives (WAS: Security gurus out there?)
>
> Or the following list, the missing referential integrity still remains
> as a MySQL nogo. MySQL is perfect for your average website, but
> definitely not for company critical data.
> Weird behaviour
> 1. You can define a varchar/char field 'auto_increment'.
> 2. SELECT 'A' = 'a' gets you true.
> 3. Int(10) is the same as int(1) eventhough the manual says
differently.
>
> 4. Tablenames are treated case-sensitive on *n?x systems, not on
> windows.
> 5. Change a piece of a table definition and mysql creates a temporary
> copy of the table, very nice if you have a 6GB table occupying a 10GB
> tablespace... (yes, the change will fail)
> 6. Adding indices result in a similar temporary copy.
> 7. What does zerofill do to a integer field? A database is meant to
> store data, not to format it while storing.
> 8. When I define a char(32) (md5-strings anyone) field, I really don't
> mean varchar(32) (MySQL automatically changes all char(X >4) to
> varchar(X)).
> 9. This is correct according to mysql: SELECT a, b, count(c) FROM d
> GROUP BY a; what will MySQL do with the b?
> 10. If you update a record and set it to the same value, mysql'll
define
> that as unaffected. Even if it does change a timestamp
> field.________________________________
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
