Re: [sqlite] lock base

2017-09-29 Thread Simon Slavin
On 30 Sep 2017, at 3:18am, MONSTRUO Hugo González wrote: > When I record a new record I must put a code equal to the major + 1. Why ? Can’t you have one table use numbers from 100 upwards and the other use numbers from 200 upwards ? Simon.

Re: [sqlite] lock base

2017-09-29 Thread Simon Slavin
On 30 Sep 2017, at 3:43am, Simon Slavin wrote: > See FAQ number 1: I’m sorry. I misunderstood the question. Please ignore that post. Simon. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] lock base

2017-09-29 Thread Keith Medcalf
nticipated traffic volume. >-Original Message- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of MONSTRUO Hugo González >Sent: Friday, 29 September, 2017 20:19 >To: sqlite-users@mailinglists.sqlite.org >Subject: [sqlite] lock base > >

Re: [sqlite] lock base

2017-09-29 Thread Simon Slavin
On 30 Sep 2017, at 3:18am, MONSTRUO Hugo González wrote: > I have a network of computers that share a SQLite file. > Two tables share sales information: current and historical. > When I record a new record I must put a code equal to the major + 1. > I need to put

[sqlite] lock base

2017-09-29 Thread MONSTRUO Hugo González
I have a network of computers that share a SQLite file. Two tables share sales information: current and historical. When I record a new record I must put a code equal to the major + 1. I need to put the database in exclusivity to avoid recording records with the same code. How I do this ?