On Sat, May 2, 2009 at 5:47 PM, brian <[email protected]> wrote: > For your purposes, why don't you simply use the conditions to keep > certain rows from being selected at all? Either that, or re-think how > you're storing this data. Why do you need to remove this or other > rows? Perhaps there's a more elegant solution.
It looks like I'll have to do it this way then. What I'm trying to do is build a event registration form, where a user sees the events he has registered on the top, and below that the events he could register. Ofcourse, in the part of the form that shows the events a user could register I don't want to show the events he has already registered. Krist -- [email protected] [email protected] Bremgarten b. Bern, Switzerland -- A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? A: Top-posting. Q: What's the biggest scourge on plain text email discussions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
