On Fri, Aug 4, 2017 at 9:21 AM, Sylvain Pointeau <[email protected] > wrote:
> On Fri, Aug 4, 2017 at 7:41 AM, petern <[email protected]> > wrote: > >> Sylvain, are you happy with the performance? >> >> Maybe you are using it differently but, from my tests, the DEFAULT clause >> is ignored for PRIMARY KEY columns. I had to use an ordinary column with >> UNIQUE constraint to test your extension. Below is a tester for 1 million >> rows which completes in about 186 seconds. The same million row test with >> PRIMARY KEY column (and ignored DEFAULT) completes in about 5 seconds. >> > > Hi Peter, > > I am not using the sequence as default, but I use it explicitely like > insert into T (T_ID) values (seq_nextval('seq')) > > I generally create few hundred rows in my app, so I won't see any > performance issue, > > Nevertheless, I am surprised to see so much difference between my UDF and > the trigger implementation. > > Does anyone have an idea how to improve it? (using the same approach -> > the sequence is in a table > I am sorry I fail to see how to improve it, I would be really interested to have advises from the experts! Furthermore, is it still useful to make a github repository since this is slow? Best regards, Sylvain _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
