On Wed, Oct 12, 2011 at 10:43 AM, herman vierendeels <[email protected]> wrote: > Should we not test also on: > > select * from lsmb12.vendor v,lsmb12.customer c where > c.customernumber=v.vendornumber;
In this case, no. Youpoint out a correct problem though. More info below. > > if so: > there will be double meta_number in entity_credit_account > > SELECT max(id),meta_number FROM entity_credit_account e group by > meta_number having count(*) > 1 order by meta_number; > > and > UPDATE lsmb12.vendor SET credit_id = (SELECT id FROM > entity_credit_account e WHERE e.meta_number = vendornumber); > will fail > > ERROR: more than one row returned by a subquery used as an expression These should be fixed on the UPDATE side by filtering on entity_class.and, in the case of vendor, entity_id. . Thanks for the bug report. Committed in svn 3849 Best Wishes, Chris Travers ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
