You don't, that's not how relational databases work. You need to create a separate field for each foreign key (student and workpiecelist) and together they form the primary key for the uniqueworkpc table. See David's reply for details.
> On Oct 20, 2017, at 9:56 PM, csanyipal <csanyi...@gmail.com> wrote: > > Hi, > > I have a small and simple database MyStudents.db . > It has three tables: *student*, *workpiecelist*, *uniqueworkpc*. > How can I manage to get primary key (pk) automatically for *uniqueworkpc* > table which is composed by pk of *student* table and pk of *workpiecelist* > table like below? > 03256789415632-2 > where > 03256789415632 > is a pk of a student in *student* table, and > 2 > is an id of a workpiece in *workpiecelist* table. > > > > ----- > Best, Pál > -- > Sent from: http://sqlite.1065341.n5.nabble.com/ > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users