RE: [PHP] Re: oo question
| From: | (Edward Peloke) | Date: | Mon, 19 Apr 2004 18:21:54 +0000 |
| Subject: | RE: [PHP] Re: oo question | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-183834@lists.php.net to get a copy of this message | ||
Chris,
Are you thinking of having a class like this for each of the tables in your
db? I am trying to build myself some reusable code and am trying to think
through the best way to do it. I have started playing with java and
hibernate and it has classes for each table so I was thinking of doing the
same thing with php.
Eddie
-----Original Message-----
From: Chris W. Parker [mailto:cparker@swatgear.com]
Sent: Monday, April 19, 2004 2:07 PM
To: Torsten Roehr; php-general@lists.php.net
Subject: RE: [PHP] Re: oo question
Torsten Roehr <mailto:roehr@zilleon.com>
on Monday, April 19, 2004 10:46 AM said:
> the second approach is definitely much, much better and the right way
> to go. But what exactly is your QUESTION?
oh yeah.. umm... i guess at this point it would be "which is better?"...
as i was writing the email it sort of went in a different direction than
i had originally planned...
> One personal suggestion: you could directly put the code from
> initialize_customer() into the constructor.
but i'm thinking that i might, at some point, want to use that method
after the object has been instantiated. i can't think of a specific
case, but i'm only imagining that it's possible.
chris.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php