Ouch--unfortunately there's nothing globally you can do to stop that. 
You *can* control specific rights in the datasource configuration for
a particular user (e.g. limit to selects only) but if they have update
rights, they can be dumb and do this.  The only way to stop it is code
reviews I suppose, and for the love of god I hope you aren't letting
the newbies hit your production database directly. ;-)

Matt

On 8/24/05, Kevin Fricke <[EMAIL PROTECTED]> wrote:
> Thanks for the info!
> 
> Another question.  Does anyone know a way to set up cf so that if you run an
> update query without a where it will error out?  I have some new help and
> this has happened twice in the last week.  Open ended queries updated the
> whole database...not good ;)
> 
> kevin
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Adrian J. Moreno
> Sent: Wednesday, August 24, 2005 9:24 PM
> To: [email protected]
> Subject: Re: mySql 5.0
> 
> 
> You think SQL Server's expensive, I'm trying to ditch Oracle. I've been
> using the 64-bit version of MySQL 4.x in production (dual Opteron) for
> almost a year and I've no doubt Oracle and MS are sweating bullets right
> about now.
> 
> Their August 2005 Newsletter came out today:
> 
> ---------------------------------------------------------------
> Products
> New Release of MySQL (5.0.11 Beta) is Now Available
> 
> This Beta release in a pre-production release in the 5.0 series.  This
> release includes support for Stored Procedures, Views, Triggers,
> Information Schema (Data Dictionary), XA and more.  Additional updates
> include:
> 
> - Security improvement:  Applied a patch that addresses a potential zlib
> data vulnerability that could result in an application crash.  This only
> affects the binaries for platforms that are linked statically against
> the bundled zlib (most notably Microsoft Windows and HP-UX)
> - Mysqldump now dumps triggers for each dumped table.  This can be
> suppressed with the –skip-triggers option.
> - Added an optimization that avoids key access with NULL keys for the
> ref method when used in outer joins.
>   - Numerous bug fixes
> 
> *All efforts are now being focused on fixing bugs and stabilizing MySQL
> 5.0 for the upcoming production release.  Get a head start on your
> projects by testing MySQL 5.0 beta now.*
> -----------------------------------------------------------------
> 
> Hopefully it'll hit GA around October. I know someone who writes their
> documentation, but he won't even give me an "I heard" date.
> 
> -- Adrian
> 
> 
> Kevin Fricke wrote:
> > that would save some serious $$.
> >
> > Thats what I am waiting for...
> >
> > Kevin
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Behalf Of Matt Woodward
> > Sent: Wednesday, August 24, 2005 6:03 PM
> > To: [email protected]
> > Subject: Re: mySql 5.0
> >
> >
> > Haven't heard anything specific but I'm anxiously awaitin this one as
> > well.  It might mean I can dump SQL Server in some cases.
> >
> > Matt
> >
> > On 8/24/05, Kevin Fricke <[EMAIL PROTECTED]> wrote:
> >
> >>
> >>Anyone heard when the expected release of 5.0 is?
> >>
> >>Kevin
> >
> >
> >
> 
> ----------------------------------------------------------
> To post, send email to [email protected]
> To unsubscribe:
>    http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
> To subscribe:
>    http://www.dfwcfug.org/form_MemberRegistration.cfm
> 
> 
> 
> 
> ----------------------------------------------------------
> To post, send email to [email protected]
> To unsubscribe:
>    http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
> To subscribe:
>    http://www.dfwcfug.org/form_MemberRegistration.cfm
> 
> 
> 


-- 
Matt Woodward
[EMAIL PROTECTED]
http://www.mattwoodward.com

Reply via email to