StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3065498
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-06-17T20:45:42.040
FavoriteCount
0
LastActivityDate
2010-06-17T20:52:42.993
LastEditDate
2010-06-17T20:52:42.993
LastEditorUserId
105019
OwnerUserId
105019
ParentId
3061621
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Okay, you're using the module autoloader in your bootstrap. It's designed to be used in module bootstraps, as it searches just one directory tree (usually a specific directory in application/modules), rather than using the include path. It can be used in the main bootstrap as an autoloader for the default module, which is why your class worked when you put it in application/models. I think you want to switch to using the standard autoloader. I'm assuming in your bootstrap class you currently have something like this: <pre><code>protected function _initAutoloader() { $autoloader = new Zend_Application_Module_Autoloader(array( 'namespace' => '', 'basePath' => dirname(__FILE__), )); return $autoloader; } </code></pre> change it to this: <pre><code>protected function _initAutoloader() { $autoloader = Zend_Loader_Autoloader::getInstance(); $autoloader->setFallbackAutoloader(true); return $autoloader; } </code></pre> this sets up the autoloader (which will also by default setup autoloading for the Zend Framework classes) and then tells it to use this autoloader for any namespace not matched by another (because your class has no namespace). With this approach you can drop any class using the PEAR naming conventions into your library directory and use it in your code. Alternatively you could do: <pre><code>protected function _initAutoloader() { $autoloader = Zend_Loader_Autoloader::getInstance(); $autoloader->registerNamespace('Model'); return $autoloader; } </code></pre> which sets up the autoloader and then tells it to use this autoloader for the namespace 'Model', which will match your Model_Login class.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLocation of DB models in Zend Framework - want them centralized
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTim Fountain
UserOwnerUserId
1. USTim Fountain
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POLocation of DB models in Zend Framework - want them centralized
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COYep - that did the trick - thanks!
 singulars
 PostPostId
 PO
 UserUserId
 USjeffkolez

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.