Yup,
Just keep a minimal include file for access to the DB's etc, then keep a
config table in MySQL, and write an interface for it. Nice idea for some
stuff (like "how many news items to show on the front page"), bad idea for
other stuff (like "server root").
I might look into something like th
: RE: [PHP] web application development question
On Fri, 26 Apr 2002, SP wrote:
> How about storing it in a database like you said with variable and value
but
> when you change a value then you write over your config.inc.php file with
a
> new one. So you get to change the value ea
Message-
From: Miguel Cruz [mailto:[EMAIL PROTECTED]]
Sent: 26 April 2002 21:19
To: Erik Price
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] web application development question
On Fri, 26 Apr 2002, Erik Price wrote:
> although include files are great for storing data that will probably not
>
ecial" - Nelson Mandela
> From: Erik Price <[EMAIL PROTECTED]>
> Date: Fri, 26 Apr 2002 16:14:43 -0400
> To: [EMAIL PROTECTED]
> Subject: Re: [PHP] web application development question
>
>
> On Friday, April 26, 2002, at 03:58 PM, Jason Wong wrote:
>
>>
On Fri, 26 Apr 2002, SP wrote:
> How about storing it in a database like you said with variable and value but
> when you change a value then you write over your config.inc.php file with a
> new one. So you get to change the value easily in a database and by using a
> file you make your app faster
.
-Original Message-
From: Erik Price [mailto:[EMAIL PROTECTED]]
Sent: April 26, 2002 4:15 PM
To: [EMAIL PROTECTED]
Subject: Re: [PHP] web application development question
On Friday, April 26, 2002, at 03:58 PM, Jason Wong wrote:
>> For those of you who write web applications (
On Fri, 26 Apr 2002, Erik Price wrote:
> although include files are great for storing data that will probably not
> change (but are now in a convenient include file in case they have to
> change), I was thinking of making this data updateable from within the
> application. So that my employer,
On Friday, April 26, 2002, at 03:58 PM, Jason Wong wrote:
>> For those of you who write web applications (in any language), what do
>> you recommend as the best way to store arbitrary atomic data for the
>> web
>> application? in other words, data that doesn't really need to be
>> stored
>>
> To: "'Richard Baskett'" <[EMAIL PROTECTED]>, "'Erik Price'"
> <[EMAIL PROTECTED]>, "'PHP General'" <[EMAIL PROTECTED]>
> Subject: RE: [PHP] web application development question
>
> Agreed, this is how I
L PROTECTED]]
> Sent: Friday, April 26, 2002 1:01 PM
> To: Erik Price; PHP General
> Subject: Re: [PHP] web application development question
>
> I usually have an info.inc file that has all these variables that I
might
> need to change. Then include it in the files that use t
I usually have an info.inc file that has all these variables that I might
need to change. Then include it in the files that use those variables and
if I ever need to change one of them I just change it in the include file
and it updates everything that way..
Rick
Beauty of whatever kind, in its
On Saturday 27 April 2002 03:50, Erik Price wrote:
> For those of you who write web applications (in any language), what do
> you recommend as the best way to store arbitrary atomic data for the web
> application? in other words, data that doesn't really need to be stored
> in a relational databa
12 matches
Mail list logo
