RE: [Phpgroupware-developers] [OT?] SQL for hosted sites

[Joseph Engo]

While this is true, again, I don't want to make the code look ugly and 
confussing.

Joseph Engo

Chris Weiss (address@hidden) wrote*:
>
>another benifit of allowing a custom table prefix would be that a site could 
>host
>more than one phpGW install in one database.
>
>Jason Wilcox (address@hidden) wrote*:
>>
>>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>But I think Tomas is asking for something from the API standpoint to
>>always append the prefix, take it out of the developers hands. For
>>instance with PostNuke you can customize what the prefix is and the
>>API takes care of appending it to the table names.
>>
>>This approach would eliminate app developers from doing it different
>>if it was added to the API. I too run in a hosted environment and
>>while I have made the necessary changes in the apps that don't
>>prepent phpgw_ to the tables, moving it to the API would mean I don't
>>have to modify code each time a release comes out, I know selfish,
>>but I never said I wasn't.
>>
>>Just my 2.5 cents
>>
>>Jason Wilcox
>>
>>- -----Original Message-----
>>From: address@hidden
>>[mailto:address@hidden On Behalf Of Dan
>>Kuykendall (Seek3r)
>>Sent: Friday, February 08, 2002 10:54 AM
>>To: address@hidden
>>Subject: Re: [Phpgroupware-developers] [OT?] SQL for hosted sites
>>
>>
>>We already do this. At least with the API and the core apps. The
>>tables all start with phpgw_ I have noticed that the lang and
>>languages tables havent been updated yet, but thats not a big deal.
>>
>>Now, some of the apps havent changed yet, but thats just a matter of
>>time
>>
>>Dan
>>
>>Tomas Sanchez Romani wrote:
>>>
>>> Hi!
>>>
>>> I'm sorry if this is off-topic or just plain stupid, but I felt the
>>>  need to give my opinion on one thing.
>>>
>>> I understand that most of the users of phpGW are able to create a
>>> new  DB exclusivly for phpGW, but some like me are hosted with one
>>> DB and  one extra would brake our extremly small budget.
>>>
>>> So my proposal is to make a change to all the sql to include a
>>> prefix  in the tablenames (the prefix should of course be
>>> configurable).
>>>
>>> ex.
>>>
>>> "insert into applications (app_name, app_title, ....";
>>>
>>> would turn to:
>>>
>>> "insert into ".$db_prefix."applications (app_name, ...";
>>> --------------^^^^^^^----
>>>
>>> this would be really great.
>>>
>>> regards, tomas
>>>
>>> ps. I'm not on the list, so please cc me.
>>>
>>> _______________________________________________
>>> Phpgroupware-developers mailing list
>>> address@hidden
>>> http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>>
>>_______________________________________________
>>Phpgroupware-developers mailing list address@hidden
>>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>>
>>
>>-----BEGIN PGP SIGNATURE-----
>>Version: PGP 7.1
>>
>>iQA/AwUBPGQFVvk3DJUEZhrQEQIv6gCdEvD4GYPSmr1p1BrEtBIk3c/e9FUAnRfp
>>qYjWTrAWUSbyaid20Wpw1XNs
>>=1Hnt
>>-----END PGP SIGNATURE-----
>>
>>
>>
>>_______________________________________________
>>Phpgroupware-developers mailing list
>>address@hidden
>>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>>
>
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>
--
    Joseph Engo <address@hidden>
    Lead developer
           __          ______                     _       __
    ____  / /_  ____  / ____/________  __  ______| |     / /___ _________
   / __ \/ __ \/ __ \/ / __/ ___/ __ \/ / / / __ \ | /| / / __ `/ ___/ _ \
  / /_/ / / / / /_/ / /_/ / /  / /_/ / /_/ / /_/ / |/ |/ / /_/ / /  /  __/
 / .___/_/ /_/ .___/\____/_/   \____/\__,_/ .___/|__/|__/\__,_/_/   \___/
/_/         /_/                          /_/