StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POOverriding PHP Class Instantiation
primarykey
Id
12923691
data
AcceptedAnswerId
12923977
AnswerCount
4
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-10-16T21:27:48.060
FavoriteCount
0
LastActivityDate
2013-02-27T19:13:04.507
LastEditDate
2013-02-27T19:13:04.507
LastEditorUserId
508666
OwnerUserId
998786
ParentId
0
PostTypeId
1
Score
1
ViewCount
294
LastEditorDisplayName
text
Body
I'm currently working on a project where we are developing an application that will be used to power content on multiple sites from a single set of files / hosting environment. There are a number of PHP classes with names such as <code>model_account</code> and <code>model_vehicle</code> which are defined in seperate files named the save as the class name. We are using <code>spl_autoload_register</code> to load the class files as below (simplified): <pre><code>function my_autoloader($class_name) { if(substr($class_name, 0, 6)=='model_') { require_once('models/'.$class_name.'.php'); } } </code></pre> What we want to do, is if the visitor is accessing site xxx and we create an instance of a class, eg <code>$account = new model_account();</code> - actually create an instance of class <code>model_xxx_account</code> if the file exists (<code>models/model_xxx_account.php</code>), but if it doesn't, just include the <code>models/model_account.php</code> file and create an instance of <code>model_account</code>. Likewise, if a visitor came from site yyy, we would want to use <code>model_yyy_account</code> if exists, but full back to <code>model_account</code> if it doesn't. Essentially what we wish to do is create an instance of a different class if conditions are met, but from the same instantiation call. We're not using an off-the-shelf framework like CI or Cake. Also, I've slightly simplified the naming conventions for this post. Sorry if my OO terminology isn't spot on.
Tags
<php><class><object>
Title
Overriding PHP Class Instantiation
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USPeeHaa
UserOwnerUserId
1. USgbuckingham89
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POOverriding PHP Class Instantiation
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI would suggest either namespaces or switching to a factory pattern, anything else will just be a quick and dirty hack.
 singulars
 PostPostId
 POOverriding PHP Class Instantiation
 UserUserId
 USMahn

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.