Let me try my hand at this... UPDATE Agora SET Winner='BobTHJ'
On 5/24/07, Ed Murphy <[EMAIL PROTECTED]> wrote:
root wrote: > On 5/24/07, Ed Murphy <[EMAIL PROTECTED]> wrote: >> root wrote: >> >> > On 5/24/07, comex <[EMAIL PROTECTED]> wrote: >> >> On 5/24/07, Ian Kelly <[EMAIL PROTECTED]> wrote: >> >> > BEGIN TRANSACTION; >> >> > >> >> > UPDATE RULE 106 >> >> > SET TEXT = 'SQL script' >> >> > WHERE TEXT = 'document'; >> >> > >> >> > COMMIT TRANSACTION; >> >> >> >> Query OK, 0 rules affected (0.00 sec) >> >> Rules matched: 0 Changed: 0 Warnings: 0 >> > >> > I beg to differ; you seem to be assuming a different database >> > organization. It seems more useful to me in this context to have rules >> > be modeled as tables rather than rows. >> >> Why? Are cursors around the corner? > > Mainly because it allows for the above syntax rather than having to > resort to all sorts of messy string manipulations. What messy string manipulations? update rules set text = replace(text,'old','new') where number = 106
