On 8/19/2015 9:24 AM, Reindl Harald wrote:
Am 19.08.2015 um 15:18 schrieb Jim:
On 8/19/2015 8:40 AM, Reindl Harald wrote:
Am 19.08.2015 um 14:29 schrieb Richard Reina:
I am writing a web application in perl that will create, edit, update
and
delete data from a MySQL database. I have written
Am 19.08.2015 um 15:18 schrieb Jim:
On 8/19/2015 8:40 AM, Reindl Harald wrote:
Am 19.08.2015 um 14:29 schrieb Richard Reina:
I am writing a web application in perl that will create, edit, update
and
delete data from a MySQL database. I have written a perl module that
will
manage the
On 8/19/2015 8:40 AM, Reindl Harald wrote:
Am 19.08.2015 um 14:29 schrieb Richard Reina:
I am writing a web application in perl that will create, edit, update and
delete data from a MySQL database. I have written a perl module that will
manage the connections (issue database handles ). As new
I am writing a web application in perl that will create, edit, update and
delete data from a MySQL database. I have written a perl module that will
manage the connections (issue database handles ). As new users sign up for
the application should each get their own MySQL username and password or is
Am 19.08.2015 um 14:29 schrieb Richard Reina:
I am writing a web application in perl that will create, edit, update and
delete data from a MySQL database. I have written a perl module that will
manage the connections (issue database handles ). As new users sign up for
the application should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/19/2015 05:29 AM, Richard Reina wrote:
As new users sign up for the application should each get their own
MySQL username and password or is okay to execute their queries
with the same (one generic) MySQL username and password?
That is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/19/2015 10:06 AM, Richard Reina wrote:
Data stored for each user would be a list of places visited that
and details relating to those trips. The type of queries they would
be able to perform be able to read, update and create new records.
