The fact that we're still discussing it tells me that extracting IGNORE is too painful for people. We should table it and move on, IMHO.
Jeremy On 9/2/08, Brian Moon <[EMAIL PROTECTED]> wrote: > > It seems to me that this is an argument for server-resident logic to > > handle error conditions rather than an imperative to crud up SQL with > > nonsensical hacks. > > > > I think in the case of MogileFS (correct me Dormando if I am wrong) and in > my case, IGNORE is used a non-blocking way to get a query run in MySQL. I > don't want to wait on an error. That is the whole point. I don't care if > the query succeeded or not in the app I am running. It is more important > that I don't have to wait for a lock or something else that will slow down > my user in the application. > > Now, is there a better solution? Maybe. I would entertain anything. But > IMO, right now, this is the best solution for this problem in MySQL. I know > Brian spoke about a generic queue within Drizzle. I am not sure what > exactly that entails, but I am up for anything that will let me send a query > and forget about it. > > -- > > Brian Moon > Senior Web Engineer > ------------------------------ > When you care enough to spend the very least. > http://dealnews.com/ > > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
