> Sean wrote : > There are existing ways to resolve this: Of course ... I was just proposing a feature which would be IMO useful for many users, I never said there were no simple way around as SPs using System tables (but having to be implemented by every firebird user)... > > 1- Rethink your schema, you could treat the "Patient" table as an > "Clinic Patient/Alias" table and define a separate "Master Patient" to > which each "Clinic Patient/Alias" entry would refer to. In this way > you only have 1 level of entries to update.
I do have a Master Patient table (PIX) but it doesn't resolve merging issues, this is a way of keeping a link between different active and valid records. Keeping old duplicate records only because they are referenced by foreign keys is not the way to go for me. And patient table was only one example, I do have the same issue with almost every single table that needs to be merged when merging databases ... and even in day to day operation a lot of tables where users can duplicate records granted they have made a typo in the identifier. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
