Extracting information from a webservice
aurelien.pralong at gmail.com
Wed Jan 23 07:01:11 PST 2013
Oops sorry, I made it too quick.
I just thought the matching between server dives and subsurface dives was
too complicated. So I just suggered, on the server side, to add an auto
incremented primary key (=PK) in the dive database (=DB), and transmit it
to clients, so matching could be easy (string comparison).
We discussed of this with Pierre, and it appeared the key for dives was a
combination of diver / dive name. Maybe this change would break DB
relationships or elsewhere ? If no, I think a row having it own key is
cleaner for databases.
2013/1/23 Dirk Hohndel <dirk at hohndel.org>
> Aurélien PRALONG <aurelien.pralong at gmail.com> writes:
> > Looks very complicated. Shouldn't we use a dedicated PK in the DB (with
> > auto increment) and return this ID in the webservice ?
> Sorry - I'm lacking context. WHAT looks very complicated? And what's a
> PK in the DB?
> You lost me
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the subsurface