18 May
2013
18 May
'13
7:47 p.m.
On 2013-05-18 18:45, Johnny Billquist wrote:
On 2013-05-18 18:35, Dave McGuire wrote:
On 05/18/2013 12:04 PM, Johnny Billquist wrote:
Is there a way we can get write access to the db? That way we can
keep our
own info up to date.
I was thinking about it. Pros and cons. Easier for updating. Potentially
anyone erasing the whole thing. The granularity of permissions is by the
whole table.
It would perhaps be possible to do something that everyone had their own
table, and then I'd just pull data from all of them for various
tasks. But
then I'd have potential name collision issues and what not...
Actually, thinking a bit more, I could probably do some web interface
with
people having their own passwords and the ability to update just
their data
that way. Needs some thinking perhaps, but maybe the most doable.
Anyone else have some ideas on how to do it?
I like the idea of giving us all write access. Maybe you can set up
regular dumps of the database for restoration in case someone screws up.
I can certainly do that. It just becomes a question of people might need
to reenter information in case a rollback has to go far. Also trickier
to realize if "corruption" actually have happened perhaps.
On the other hand, I could atleast have permissions that only allowed
random people to modify data, not add new, nor delete.
One thing I always like to have is some kind of uniformity. That is always harder to get
with many people entering data. But I guess that can be addressed by having some explicit
guidelines.
Right now, the uniformity (as far as it goes) comes from just my head.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic
trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" -
B. Idol