On Sat, 2013-10-05 at 17:23 +0200, Fernando Martins wrote: > On 10/05/2013 02:08 PM, Willy Raets wrote: > > > > Then adding a primary key should solve that problem. > > > Indeed, that is the practical solution, but it is an artificial solution > because in _theory_ each tuple should represent a unique entity. In the > UI, how do you distinguish one record from the other? it's like the UI > has some information about the record which does not exist in the table.
There is no need to distinguish on record from another. Only thing that is important is that the number of records with the same ID are the same as the number mentioned in the main table with this ID. But the problem is solved (see other post) using a 'SELECT .... limit 1' -- Kind regards, Willy (aka gbWilly) http://gambasshowcase.org/ http://howtogambas.org http://gambos.org ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
