[EMAIL PROTECTED] wrote: > hi all, > > i have a problem with the current project i am working on.actual thr's > a table X with a field ID(autoincrement) and a field named HASH.which > is md5 of the id.now should i have to make two queries ..first one to > find out whats going to be next id and then insert the hash of it ..or > there is anotherway to do it.In SQL it world fine if i execute > following statement : > > SET @max_id=(SELECT max(ID) from table_X);insert into table_X(HASH) > values(md5(@max_id+1)); > > so please tell me a good solution ..i don't want to query two time.btw > i am using mysql as database backend.
A good solution is somewhat dependent on understanding the problem. Why do you need to store an md5 of the ID? a shot in the dark solution is: create a db trigger SET hash = md5(id) (not sure exactly the trigger syntax, but mysql does have an md5: http://dev.mysql.com/doc/refman/5.1/en/encryption-functions.html#function_md5 Carl K --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
