SELECT MIN(TableName) as TableName, ID, COL1, COL2, COL3 ...
SELECT 'Table A' as TableName, A.ID, A.COL1, A.COL2, A.COL3, ...
SELECT 'Table B' as TableName, B.ID, B.COL1, B.COl2, B.COL3, ...
GROUP BY ID, COL1, COL2, COL3 ...
HAVING COUNT(*) = 1
ORDER BY ID
That shows any row that exists in Table A and that doesn't exist in Table B,
It's incredibly efficient because it uses UNION.
I will report back in a few days/weeks to tell you guys if this way is a
convenient way to by-pass implementing the bit-mask system manually.
2008/2/12, Jonathan Carse <jonathan.carse@gmai...>:
> Hey Eric,
> Yes, we are offering the same solution, and both ways will work fine.
> The difference, as you correctly pointed out, is that your solution does
> writes during desktop activity, while my solution does writes during sync
> activity. It's the same result, you are correct.
> It is a lot easier for me to implement the changes on my conduit project
> than on my desktop project, and that is the only reason I lean towards my
> own solution.
> Another developer working on a different project might find it easier to
> implement the changes on the desktop project.
> Our project is aimed at the home user. So an SQL server solution seems
> irrelevant - no home user will accept software into his/her home based on
> the condition that an SQL server is installed as well.