This is a discussion on DROP TABLE customers within the MySQL Database forums, part of the Database Forums category; Rik Wasmus <luiheidsgoeroe@hotmail.com> writes: > Ignoramus26246 wrote: >> I would like to know if Perl'...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Rik Wasmus <luiheidsgoeroe@hotmail.com> writes:
> Ignoramus26246 wrote: >> I would like to know if Perl's DBI supports an attribute that would >> make a database handle read only. >> >> That is, I am looking for a way to make a handle read only so that all >> subsequent queries that seek to modify the database, would not proceed >> at all. >> >> This would be for mysql. > > A better way would be to make a user with only select priviliges, and > no insert/update/drop privilige. An even tighter method, if you're using a version of MySQL that supports stored procedures, is to use them to define an API for access to your data. Then you can give a user permission to execute your API procedures, and no low-level access at all. sherm-- -- My blog: http://shermspace.blogspot.com Cocoa programming in Perl: http://camelbones.sourceforge.net |
|
|||
|
On May 9, 11:11 am, Ignoramus26246 <ignoramus26...@NOSPAM.
26246.invalid> wrote: > I would like to know if Perl's DBI supports an attribute that would > make a database handle read only. mysql> GRANT SELECT ON database.* TO 'webuser'@'localhost' IDENDIFIED BY 'webuserpassword'; Then, use webuser as your user for your application. CC |
|
|||
|
On Fri, 09 May 2008 19:59:35 +0200, Sherman Pendley <spamtrap@dot-app.org>
wrote: > Rik Wasmus <luiheidsgoeroe@hotmail.com> writes: > >> Ignoramus26246 wrote: >>> I would like to know if Perl's DBI supports an attribute that would >>> make a database handle read only. >>> >>> That is, I am looking for a way to make a handle read only so that all >>> subsequent queries that seek to modify the database, would not proceed >>> at all. >>> >>> This would be for mysql. >> >> A better way would be to make a user with only select priviliges, and >> no insert/update/drop privilige. > > An even tighter method, if you're using a version of MySQL that supports > stored procedures, is to use them to define an API for access to your > data. > Then you can give a user permission to execute your API procedures, and > no > low-level access at all. Well, that's of course less tight then no alteration whatsoever, but indeed a very usefull one to keep basic functionality and alterations going with a limited user while keeping integrity. -- Rik Wasmus [SPAM] Now temporarily looking for some smaller PHP/MySQL projects/work to fund a self developed bigger project, mail me at rik at rwasmus.nl. [/SPAM] |
![]() |
| Thread Tools | |
| Display Modes | |
|
|