Wel guys, thanks for the advice. I guess my own custom CGI would work, or
something similar. Your help has been greatly apreciated. I was merely trying to
find out if its possible to do it any other way, and you guys have already given
me some stuff to think about. Cheers!
Dan
Lincoln Yeoh wrote:
> At 10:12 PM 3/10/01 -0500, Dan McGrath wrote:
> >Thanks Tom. Actually its kinda holding me off really bad. I would like to
> >switch to mysql, but I still feel confident in pgsql to stay. One fellow on
> >irc I talked with mentioned the possibilty of creating a trigger on the
> >internal pgsql tables to restrict adding or creating anything. I just think
> >its very bad for me to consider opening my db to the world with that kind of
> >access open to the public. Would be like hotmail allowing unlimited email
> >size. You get my idea anyways Im sure.
>
> I doubt that I would ever recommend opening any RDBMS to the world.
>
> There is a very high chance that even if controls are put in, there will be
> ways around it.
>
> It's as bad as giving a unix/cmd shell to the world.
>
> Aren't there other ways to do what you want without giving the world access
> to your database?
>
> Maybe each user could have their own postgresql engine running on their own
> server (real or virtual).
>
> Cheerio,
> Link.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl