I have over three decades of dealing with SQL and I can still not understand how this myth got propagated.
There is NO valid SQL reason why a table should be required to have a unique primary key or any predefined key for that matter. One can always use the row number (record number) if such a key is required for one's application. On 03/28/2015 12:31 PM, gam...@googlecode.com wrote: > Updates: > Status: Accepted > > Comment #4 on issue 612 by benoit.m...@gmail.com: BUG Cannot browse more of > 128 records on tables "No current connection" > https://code.google.com/p/gambas/issues/detail?id=612 > > The reason why DataBrowser or DataView fails is because your table does not > have a unique primary key. This is mandatory, otherwise DataBrowser or > DataView can't work correctly. > > I will modify them in the future so that they raise an explicit error if no > unique primary key is found. > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
