We've been using transfer on an application successfully for a while now, but have just moved it into a clustered environment, and now are having trouble. Transfer generates the primary keys for a couple of tables, 'events' and 'venues' this is because both those tables can also be updated from a data import, which carries its own IDs. The problem is that Transfer doesn't seem to reference the transfer_sequence table in the DB before it creates an ID, so we're getting duplicates. When each instance writes to the DB, it seems to generate an ID from memory, then updates the transfer_sequence table with that ID. So, of course, when the other instance then writes, it frequently uses the same ID. The only other thing of note, is that the ID column used, isn't actually the PK, could this make a difference?
So, is there a way of getting Transfer to always consider the generated ID to be Dirty and retrieve a new one from the DB each time? Many Thanks, Alex -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" 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/transfer-dev?hl=en
