Doctrine Project

[PHPCR-110] getAssociationTargetClass targetDocument not set

Mon, 13 May 2013 20:50:00 +0000

follow up of https://github.com/doctrine/phpcr-odm/pull/279

ClassMetadata

// TODO this may be not set. what happens if we would return null then?
return $this->mappings[$fieldName]['targetDocument'];

investigate and fix once 279 is merged.

[PHPCR-109] Why Generic::getNodename and not camelcase?

Mon, 13 May 2013 20:48:39 +0000

Is there a reason why the get node name method on the generic document is ->getNodename and not ->getNodeName?

[PHPCR-108] suport entity listeners resp document listeners

Sun, 5 May 2013 07:42:37 +0000

see http://docs.doctrine-project.org/en/latest/reference/events.html#entity-listeners

[PHPCR-107] Support for ->sameNode type queries in QueryBuilder/ExpressionBuilder

Thu, 25 Apr 2013 16:40:07 +0000

We should support sameNode operator of the QOMFactory in the QueryBuilder.

An example using the PHPCR QB from the DoctrinePHPCRAdminBundle:

Unable to find source-code formatter for language: php. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

        $qb = $queryProxy->getQueryBuilder();
        $qmf = $qb->getQOMFactory();

        $constraint = null;
        foreach ($idx as $id) {
            $path = $this->getBackendId($id);
            $condition = $qmf->sameNode($path);
            if ($constraint) {
                $constraint = $qmf->orConstraint($constraint, $condition);
            } else {
                $constraint = $condition;
            }
        }
        $qb->andWhere($constraint);

[PHPCR-106] Make getRefererrs return not-yet-flushed referring documents

Thu, 18 Apr 2013 13:03:25 +0000

Currently the DocumentManager->getReferrers() method returns only referrers that have already been flushed to the database.

It is (I think) desireable for this method to return also those objects which have been added to the UnitOfWork but have not yet been flushed to the database.

[PHPCR-105] ensure xml and yml naming conventions are consistent

Fri, 19 Apr 2013 12:07:23 +0000

for yml, all mappings must use camelCase, while for xml it must be connected-text in all lowercase with the dash between. it seems at least fieldName is wrong.

we should clean this up before the first release to avoid having to deal with inconsistent legacy from the beginning.

[PHPCR-104] implement unitofwork isScheduledDocument

Tue, 19 Mar 2013 12:41:05 +0000

as discussed in https://github.com/doctrine/phpcr-odm/pull/268 we should implement UnitOfWork::isScheduledDocument and isScheduledFor* other than isScheduledForInsert.

[PHPCR-103] map node autoname feature

Thu, 14 Mar 2013 09:30:48 +0000

we should map the Node::addNodeAutonamed as an option for the nodename field to have nodes that generate their own name (i.e. useful in children collection)

[PHPCR-102] DocumentManager::reorder can not be called multiple times for the same parent

Fri, 19 Apr 2013 11:10:20 +0000

unless i really misread the code in UnitOfWork::scheduleReorder, trying to reorder more than one child of the same parent document will drop the previous reordering.

the whole method is of limited use, as you can also reorder the children in the ChildrenCollection.

[PHPCR-101] MissingTranslationException when parent is not translated

Thu, 18 Apr 2013 12:53:58 +0000

Getting a MissingTranslationException when displaying a banner on the frontend. It seems to be caused in the refreshDocumentForProxy method on line 496 of UOW, the parent document does not have a locale and therefore the fallback hint is false. The banner block is not translated and the banner images are (title property).

See for a stacktrace: https://gist.github.com/rmsint/2c6700e00c47c95dc30e

[PHPCR-100] The mixin `jcr:lastModified` is not updated

Fri, 19 Apr 2013 10:29:13 +0000

If the document have `jcr:lastModified`, this attribute is filled on create but not updated when a document is modified.

I tried to set manually this attribute and it is not updated too.

[PHPCR-99] Support configuring mixin node types

Thu, 18 Apr 2013 12:51:38 +0000

we should have a document level mapping to declare arbitrary mixins (like mix:created and mix:lastModified to have autogenerated timestamp fields that then can be mapped)

[PHPCR-98] replace child document

Sat, 2 Mar 2013 11:59:43 +0000

when replacing a mapped child with a new document, we get the cannotMoveByAssignment exception, which imo is a) the wrong message as its not about setting a tracked document to become a child somewhere else but what we should do is delete the existing child document and add the new one.

this happens at https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L1912

for multiple children, i am less sure how it should work, if it is possible the same way:
https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L935

[PHPCR-97] Allow QB / XB to sepcify objects as targets

Wed, 20 Feb 2013 18:21:46 +0000

Allow the query builder expression to specify an object as a target.

Unable to find source-code formatter for language: querybuilder. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

$qb->where($qb->expr()->eq('someObjectReference', $someObject);

So if the target passed is mapped and it is referenceable then replace the object instance with its UUID.

[PHPCR-96] Clean up event argument classes

Thu, 18 Apr 2013 14:49:25 +0000

clean up the event argument classes to only use specific classes if needed, and base on doctrine commons events

see https://github.com/doctrine/phpcr-odm/pull/246 and https://github.com/doctrine/phpcr-odm/issues/245

[PHPCR-95] Support parameter binding in QueryBuilder (depends Jackalope support)

Tue, 12 Mar 2013 14:18:20 +0000

Parameter binding is not currently implemented in the QueryBuilder, and the comments seem to indicate that this is because jackalope does not support it at the moment.

[PHPCR-94] Implement ->iterate on Query object

Tue, 19 Feb 2013 22:15:30 +0000

Implement the Query->iterate method which will return an IteratableResultSet as per the ORM.

[PHPCR-93] Implement ->clone() method on Query object

Tue, 19 Feb 2013 22:13:45 +0000

As with the ORM query object, implement the ->clone() method.

[PHPCR-92] Join support in QueryBuilder

Tue, 19 Feb 2013 22:14:26 +0000

Joins are currently not supported in the QueryBuilder, the methods are there and some of the logic is partially coded, but they just havn't been implemented.

At time of writing joins are not supported by doctrine-dbal (i think) but they are supported at least by Jackrabbit.

[PHPCR-91] getSIngleResult throws ambiguous Exception

Thu, 18 Apr 2013 13:12:06 +0000

Query->getSingleResult correctly throws an Exception when there are no results (or more than one), but it is an Exception that could also be produced by other things, so not guaranteed to mean that (
(http://docs.doctrine-project.org/projects/doctrine-phpcr-odm/en/latest/reference/query.html#getsingleresult)

[PHPCR-90] referrer delete and cascade delete

Tue, 12 Mar 2013 17:04:17 +0000

currently, removing an entry from the referrer collection has no effect, nothing is deleted.

without cascading, we should delete the value from the referencing property (needs the filter(mappedBy) attribute again), with cascading we should delete the referencing document.

[PHPCR-89] child documents are not translateable?

Thu, 18 Apr 2013 12:58:03 +0000

I just tried the odm on a testproject. but i have a really strange problem with translations. if i add a document which has children - and then try to add a translation to the children documents - the translation will not be saved .... (i tried the same with the symfony cmf - same result )
code:

[PHPCR-88] locales mapping for language fallback: do not repeat language

Thu, 18 Apr 2013 12:49:12 +0000

currently the language fallback is defined like this

locales:
en: [en, de]
de: [de, en]

the first option must be the requested language. this is counterintuitive and error prone. saying "en: [de]" would make english always only try german. we should add the locale itself as first locale i think, i see no use case of defining fallbacks where the requested locale is not the one to be preferred.

[PHPCR-87] the document manager did not return a result for findBy(array('id' => 'some/id')) but does for find('some/id')

Fri, 19 Apr 2013 10:26:14 +0000

the document manager did not return a result for findBy(array('id' => 'some/id')) but does for find('some/id')

[PHPCR-86] QueryBuilder QOMFactory access

Tue, 15 Jan 2013 10:22:42 +0000

There is getQOMFactory method in PHPCR\Util\QOM\QueryBuilder (very useful) but it isn't in Doctrine\ODM\PHPCR\Query\QueryBuilder (it breaks bc).

Is it mistake or there is/will be another method to access QOMFactory instance?

[PHPCR-85] implement querybuilder hydrate array option

Mon, 14 Jan 2013 09:12:13 +0000

the query builder can currently hydrate to documents and to phpcr nodes. it should also be possible to hydrate the result into a plain array to avoid creating documents and get the direct query result. (btw note that '*' in sql2 does not mean all properties of a document, but just the path and some other basic things - you always need to specify all fields you want to retrieve explicitly in this case)

for the query builder base work and discussion see https://github.com/doctrine/phpcr-odm/pull/204

[PHPCR-84] make the query API work with i18n

Tue, 14 May 2013 07:07:33 +0000

when searching there must be some way to ensure that for translateable documents the right fields are filters. f.e. when using the child strategy then for the given columns the node name needs to be checked (nodename = phpcr_locale:fr). for attributes strategy the property name needs to be rewritten ("title" vs "phpcr_locale:fr-title").

it might not be possible to easily automate this.

[PHPCR-83] make the test suite run and pass with Doctrine DBAL

Reference — Fri, 11 Jan 2013 15:13:59 +0000

this will likely require some work to disable certain tests relying on features not yet implemented

[PHPCR-82] add support to check if a multivalue property of type array actually changed or not

Thu, 18 Apr 2013 13:06:16 +0000

right now we only really support checking the dirty state of MultivaluePropertyCollection instances. however in some cases it might be necessary to convert things to an array, even if there are no actual changes. therefore it would be good to also check the dirty state in case of an array

[PHPCR-81] Referrers should not return the frozen node of a version in version storage

Wed, 26 Sep 2012 10:25:58 +0000

In the document of phpcr.github.com (http://phpcr.github.com/doc/html/phpcr/nodeinterface.html#getReferences%28%29), I quote:

"In implementations that support versioning, this method does not return properties that are part of the frozen state of a version in version storage."

But, the referrers returns some versioned node.

[PHPCR-80] ChildrenCollection is not updated after flush although children where added before

Tue, 12 Mar 2013 14:10:07 +0000

If you create children of a document without adding them to the children collection of the parent (with a children annotation) the children collection is not updated after flush, you need to call $dm->clear() to force a reread of the children. The current case was with a parent and its children created in the same flush.

[PHPCR-79] metadata type for non-property mappings

Mon, 14 Jan 2013 23:13:29 +0000

(this is a follow up of https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/issues/56)

ClassMetadata::mapField does not automatically assign a type except for the id field. we should add them here to have type information for things like nodename so for example sonata admin (or the symfony form builder?) can use that information to decide on the widget to use.

open question: is there a natural type mapping for children/parent? should we use MANY_TO_ONE for parent and ONE_TO_MANY for children? or is that a problem as its not arbitrary relations, should we add new types for this?

[PHPCR-78] Exception "Can't remove the protected property: jcr:created" on persist

Thu, 30 Aug 2012 09:12:46 +0000

When a Document contains a reference field (tested with @ReferenceMany(strategy="hard"), @ReferenceOne(strategy="hard")) and a "jcr:created" field in its metadata, then phpcr-odm try to update the protected field (jcr:created) to NULL on persist.

Jackalope throws the following exception :

[PHPCR\NodeType\ConstraintViolationException]
Can't remove the protected property: jcr:created

[PHPCR-77] document level options inheritance

Sun, 5 May 2013 07:54:47 +0000

documents extending other documents should inherit the global attributes unless overwritten explicitly.

for example, having @Document(referenceable=true) should be kept for an extending class unless it explicitly sets it to false. currently, attributes are reset on each new @Document tag. (i assume we have the same issue for xml/yml mapping?)

[PHPCR-76] add support for Selectable in PersistentCollection

Thu, 18 Apr 2013 13:06:48 +0000

add support for Selectable in PersistentCollection

[PHPCR-75] Mapped Superclass cleanup and documentation

Thu, 10 Jan 2013 12:02:42 +0000

this is a follow-up for https://github.com/doctrine/phpcr-odm/pull/144#issuecomment-7096029

we need to check if mapped superclass is working as it should, and then clarify the doc at https://github.com/doctrine/phpcr-odm-documentation/blob/master/en/reference/inheritance-mapping.rst

i still did not understand what exactly the feature means.

[PHPCR-74] [translations] allow detached document with locale propagation to mapped associations

Fri, 1 Feb 2013 10:20:08 +0000

managed documents can only ever exist once per DocumentManager, and thus only in one language. for this reason we did not want to make the language propagate for mapped children and references (as this would change the content of documents in a hard to understand way - and loading anything in a different language again would still lose the language)

thus we should provide a findTranslation variant to get a detached translated document that fetches all associations as detached as well, keeping the locale setting.

there is no way to handle the write case, but this would cover the read case.

[PHPCR-73] add support for custom ID generators

Tue, 12 Mar 2013 14:17:05 +0000

https://github.com/doctrine/doctrine2/pull/206

[PHPCR-72] persist cancels move

Sat, 21 Jul 2012 07:54:08 +0000

If i have a node that i fetch from the repo using $dm->find()

If i change an attribute in it.
Then i call $dm->move() on it

Then i call $dm->flush().

It will work.

However if i call $dm->persist() on the node (that i already fetched from $dm->find()) and then call $dm->flush()
The $dm->move() won't occur, it will be cancelled, but the attribute i changed will still be updated.

[PHPCR-71] refactor exceptions

Thu, 18 Apr 2013 13:09:42 +0000

https://github.com/doctrine/phpcr-odm/pull/144#discussion_r963877 reveiled that we should look into the exception concepts and streamline them.

[PHPCR-70] ContentDocument Relationships returning NULL in Action

Sat, 21 Jul 2012 14:26:04 +0000

So i have 2 Documents:

Page: http://pastebin.com/b5X32JPc

Category: http://pastebin.com/A1gB6kyg

A Category has many pages.

Now here's my (test) action: http://pastebin.com/ypjxqZPu

As you can see, $contentDocument is a page in this case. If i call $contentDocument->category i get back "null".

If however i tell the document manager to fetch the Page document by it's path, then $contentDocument->category will work...

Our conclusion is that if you take the $contentDocument that is passed to your action, and you try to fetch it's ParentDocument inside the action (mapped to a property) you always get null.
However, what is very weird, is that inside twig it works (page.category would work in twig but page->category would return null inside the action, before the twig render)

[PHPCR-69] persist referrers

Fri, 11 Jan 2013 08:53:40 +0000

phpcr knows reference and referrer (backlink). the reference is a property of a node with a defined name. the referrer is an information on the node without a property name in PHPCR. we have the annotation @Referrers to map this information onto a document field. the annotation can take an optional filter argument to only use references pointing to this node with a specific phpcr name.

we could add something like the cascade option found in the orm to allow assigning a document to a referrer property and automatically persist it. we will need to explicitly specify the reference property name to be used on the source document in this case (orm uses mappedBy for this)

github user mdekrijger started working on this. today, he wrote: Adding the annotations was quite easy, still figuring out the unitofwork where the actual processing must be implemented. Currently I can't spend much more time on it until end of june. If it isn't done yet by that time, I surely will pick it up from there.

[PHPCR-68] Versionable Item completely loses references

Sun, 22 Jul 2012 19:29:02 +0000

I have a post that has a reference to a subcategory

When i made my post versionable="full", the current and old versions of post lost this reference.

So when i call $post->subcategory i get back a Generic ODM document instead of a Subcategory Document

I know that relationships are not versionable, but relationships should at least still exist.

The workaround is to get the parent path and make a JCR-SQL2 query to fetch the subcategory document.

[PHPCR-67] Fetching a node beforehand ruins ordering of collections

Sun, 22 Jul 2012 19:24:30 +0000

Two documents: Category and Subcategory
Category has $subcategories as a PHPCRODM\Children

If Category A has 3 subcategories B1 B2 B3.

If A's subcategories are fetched we would receive them in the following order: B1 B2 B3.

Now if however we fetched the B2 node using the DocumentManager at an earlier line and then fetched the subcategories of A, we would receive them in the following order:
B2 B1 B3

[PHPCR-66] handle ParentDocument and Name changes as move operations

Tue, 5 Jun 2012 11:49:54 +0000

changes to the @ParentDocument and @Name should be translated to move operations. they are the most natural way to move a document in a form.

[PHPCR-65] find with uuid creates duplicate of document

Fri, 20 Jul 2012 07:51:56 +0000

i am pretty sure the DocumentManager::find() method creates a duplicate document each time you request the document by uuid. it should not just load the node but convert that node to a path and then do the check if the document is cached. if the node is already cached the lookup by uuid is cheap. if not, it is now cached and the lookup by path is cheap. so no overhead, but eliminate the risk of having several instances of the same document.

https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/DocumentManager.php#L279

[PHPCR-64] add support for child prefetching

Wed, 18 Jul 2012 22:07:48 +0000

https://github.com/jackalope/jackalope/pull/113

the idea would be to set the depth via a mapping on a per model or per collection basis

[PHPCR-63] event system: prePersist and postPersist

Tue, 22 May 2012 11:20:46 +0000

according to http://docs.doctrine-project.org/projects/doctrine-orm/en/2.1/reference/events.html#prepersist the persist event is only triggered when persisting a new entity/document. but currently the phpcr-odm uow triggers it during the flush operation.

we have to go over the event system and clean that up.

[PHPCR-62] avoid dereferencing proxies on save

Tue, 10 Apr 2012 08:47:37 +0000

chregu found in a large project that the odm seems to resolve all unresolved proxy documents during flush, even if the @ReferenceMany or @Referrer was not touched by the code.

we should make sure this does not happen.

[PHPCR-61] review how the ORM and other ODM's initialize collection properties

Thu, 18 Apr 2013 12:47:02 +0000

right now when we for example have a @ReferenceMany but nothing is assigned, then when we read said object from the database that property is set to null. should it rather be initialized as an empty collection?

[PHPCR-60] add finalize step to mapping to calculate and validate

Thu, 4 Oct 2012 21:33:40 +0000

follow up of the discussion in https://github.com/doctrine/phpcr-odm/pull/120

id strategy:

1. if there is an id with a strategy always use that
2. if not and there is a parent and a node name mapping use the parent strategy
3. else use assigned strategy if there is an id field
4. throw an exception that you can't use this document

finalizing the mapping could have the added benefit of combined validation. for example if assigned strategy is parent and name but there is no field mapped to the name, it would tell this is invalid.

think what should be validated at the finalize point.

[PHPCR-59] have a strategy for ReferenceOne/Many PATH to make it relative

Mon, 8 Oct 2012 07:34:03 +0000

this is a follow-up of
https://github.com/doctrine/phpcr-odm/pull/116

i think a user might need to attach his own strategy to the document manager. we could call this path_relative= and provide "max" that string-compares the target path and the node path and puts as few ../ as necessary. but again this does not block this pull request.

[PHPCR-58] figure out how to handle dangling weak/path ReferenceOne/Many properties

Wed, 7 Mar 2012 17:20:35 +0000

this is a follow-up of
https://github.com/doctrine/phpcr-odm/pull/116

the problem is: what happens when a ReferenceOne path or weak reference property points to something non-existing? is the property null? is the currently invalid reference removed on save or kept (which would make sense, in case the node at path appears later). but if it is usually kept, how can we delete it if we want?

[PHPCR-57] do not track the original/unmapped values separately

Sat, 3 Mar 2012 21:30:00 +0000

instead we should just use the current state of the underlying node.

[PHPCR-56] Support Hashmaps in fields

Reference — Mon, 22 Oct 2012 14:57:24 +0000

we should have an annotation to have multivalue properties be hashmaps, that is arrays with custom keys that get preserved. there are 3 options:

two multivalue fields with keys and values respectively. see i.e. https://github.com/symfony-cmf/symfony-cmf/pull/140 (another workaround can be to use the @PostLoad and @PreUpdate hooks to split/merge the arrays)
serialize the array into a string field
child nodes (performance penalty). they would need to be in a special namespace to be identifyable and have a special format. a node for key-value is a lot. if you want a document with a specific name, you should use child documents directly, not a hashmap with document entry.

[PHPCR-55] Add mapping for maps/associative arrays

Sun, 26 Feb 2012 16:37:36 +0000

Add a mapping for maps or arrays. Either implement as child node or serialize the array to a string. The first approach needs another node being fetched from the repository but allows to search the array.

[PHPCR-54] Implement LazyLoad for MANY_TO_ONE referenced docs

Wed, 22 Feb 2012 09:28:54 +0000

MANY_TO_MANY referenced are now only loaded on demand (see ~~PHPCR-52~~) via the ReferenceManyCollection. But MANY_TO_ONE are not yet, to be implemented

[PHPCR-53] repository::createDocument is never called

Wed, 22 Feb 2012 07:51:06 +0000

i tried using repositories. see

https://github.com/symfony-cmf/ChainRoutingBundle/commit/12515f82b02c4a1ef230b05133ec89e03c1af2e0
https://github.com/symfony-cmf/ChainRoutingBundle/commit/edd9f9544eadedb142fefd3ea9bb0c3b293c59d5

however, from looking at the uow code i have the impression that createDocument is never called on DocumentRepository but directly in UOW. shouldn't the uow fetch the repository and build the document with the repository? effectively moving UOW::createDocument impl. to the base repository?

[PHPCR-52] lazy loading of ReferenceMany fails

Wed, 22 Feb 2012 14:57:38 +0000

When I have a document with ReferenceMany "Links", Doctrine PHPCR always loads all those referenced documents, even if I just load the main document. This is obviously very bad for performance.

https://gist.github.com/1838831
is a reproducible use-case. Just ran it twice and you'll see that in the second run, there is

one GET request for the initial documents
a REPORT request for every referenced document to resolve the UUID to a path
a POST request for multi-get-ing all the referenced documents

See also this charles-screenshot
https://img.skitch.com/20120215-8572c4s5mc8gt2da5wjd71512w.jpg

I have no idea where to look at to fix this, so any help would be very appreciated

[PHPCR-51] make it possible to add attributes to type mappings

Thu, 16 Feb 2012 16:48:34 +0000

f.e. make it possible to make a string mapped typed translatable inside an inherited class
this will require modifications to the ClassMetadata class:
https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/Mapping/ClassMetadata.php#L578

[PHPCR-50] fix handling of children on update

Thu, 12 Apr 2012 20:40:12 +0000

right now we do not check if individual elements in the collection have been added or removed. furthermore since we can now update the order of children in jackalope, we can implement this in collection persistence as well.

[PHPCR-49] rewrite DocumentRepository::createQuery() to use QOM

Fri, 10 Feb 2012 17:46:43 +0000

https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/DocumentRepository.php#L253

[PHPCR-48] add a way to move() nodes

Mon, 13 Feb 2012 13:45:04 +0000

add a way to move() nodes

[PHPCR-47] make it possible to disable exceptions for phpcr implementations without versioning support

Reference — Wed, 14 Nov 2012 10:49:45 +0000

so method calls to checkPoint() etc shouldn't fail. full versioning should just set referenceable etc.

[PHPCR-46] ensure that parent mappings are populated after flush

Fri, 20 Jul 2012 07:59:34 +0000

https://github.com/doctrine/phpcr-odm/pull/97#r410832

[PHPCR-45] add ability to prime collections

Thu, 18 Apr 2013 13:08:19 +0000

https://github.com/doctrine/mongodb-odm/commit/2da6e9c92d515edae7c63233740349e0d272b19b

[PHPCR-44] implement configurable change tracking

Mon, 8 Oct 2012 07:33:36 +0000

http://www.doctrine-project.org/docs/orm/2.2/en/reference/change-tracking-policies.html

[PHPCR-43] Custom data type

Reference — Thu, 19 Jul 2012 18:27:59 +0000

It will be great to be able to store array as a json in a property. There is no way to define custom mapping type (it is possible with doctrine ORM)

[PHPCR-42] sync the xml/yml mapping driver with the annotation driver

Fri, 17 Aug 2012 08:17:16 +0000

especially the locale/version stuff is not yet supported. but also the reference mapping seems to look quite different.

[PHPCR-41] MappingException: Class Doctrine\ODM\PHPCR\ReferrersCollection is not a valid document or mapped super class.

Sun, 8 Jan 2012 19:43:06 +0000

reported by nacmartin https://github.com/symfony-cmf/symfony-cmf/issues/131

Since this property was introduced

https://github.com/symfony-cmf/symfony-cmf/blob/master/src/Symfony/Cmf/Bundle/ContentBundle/Document/StaticContent.php#L44

I have this error when persisting this kind of document in SAB:

MappingException: Class Doctrine\ODM\PHPCR\ReferrersCollection is not a valid document or mapped super class.

Any clue?

=> phpcr-odm should not try to persist a ReferrersCollection. this is just the inverse of the Reference annotation. as this is directional in phpcr, the ReferrersCollection should be immutable by the client.

[PHPCR-40] implement inheritance inside find()

Mon, 18 Feb 2013 18:11:40 +0000

meaning if B extends A and someone does ->find('A') that it would find instances of B
this will require changes to ClassMetadataFactory::doLoadMetadata()
https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/Mapping/ClassMetadataFactory.php#L119

[PHPCR-39] support ArrayCollection with References/Referrers

Fri, 3 Feb 2012 07:31:31 +0000

support ArrayCollection with References/Referrers

[PHPCR-38] make it possible to inject a custom UUID service

Thu, 19 Jul 2012 18:27:11 +0000

right now we have hardcoded \PHPCR\Util\UUIDHelper::generateUUID(), but that is a very simplistic implementation and the spec is much broader ..

[PHPCR-37] update for latest doctrine common features

Wed, 28 Dec 2011 23:28:15 +0000

see

https://github.com/doctrine/common/pull/71
https://github.com/doctrine/common/pull/75
https://github.com/doctrine/common/pull/83
https://github.com/doctrine/common/commit/07d2f04408534f0870d9873a420e294a4b0db439 (done)

as well as https://github.com/doctrine/couchdb-odm/commit/56f4ce911c9fd7cf32547a9d454141f250c9de54 (done)

[PHPCR-36] Provide migrations tool

Reference — Mon, 8 Oct 2012 07:31:08 +0000

when i have existing content and later change the document class to have referenceable=true, this is not updated even on persisting the document again.

uwe: I think there are several other things that fail when you have existing content in the repository - maybe the solution to think about is something like migrations ... that would prevent the performance penalty on ordinary code and still give you the change to change the structure of your documents.

things that come to mind

change document class name
removing fields
change field type
bulk changing the values in some field
everything related to node types (though, as an additional challenge at least jackrabbit does not allow to remove things from node types through the davex remoting we use in jackalope)

[PHPCR-35] referenced documents need to be referenceable

Wed, 28 Dec 2011 23:31:59 +0000

currently documents referenced need to have referenceable=true in their document annotation, otherwise the @ReferenceOne silently fails. (see also https://github.com/symfony-cmf/cmf-sandbox/pull/29 )

either phpcr-odm should complain. or it could just add the mix:referenceable to the target document even though it was not declared referenceable.
we could additionally make referenceable=true the default and offer explicit referenceable=false for optimization.

[PHPCR-34] replacing a document fails

Wed, 22 Feb 2012 15:03:39 +0000

when we have a saved document and remove that, then add a document at the same path without a flush in between, we get an exception. the reason is that persist already adds the phpcr node, but scheduleRemove does not remove the phpcrnode right away.

the fix looks like it should be:
UnitOfWork.php 504 remove phpcr node - 1022 do not remove here as it was removed before.

but this leads to a problem that is either in jackalope or the phpcr-odm about /functional/user/phpcr:class being not found.

1) Doctrine\Tests\ODM\PHPCR\Functional\BasicCrudTest::testRemoveAndInsert
PHPCR\ItemExistsException: This node already has a child named user.

/home/david/liip/symfony-cmf/cmf-sandbox/vendor/symfony-cmf/vendor/doctrine-phpcr-odm/lib/vendor/jackalope/src/Jackalope/Node.php:303
/home/david/liip/symfony-cmf/cmf-sandbox/vendor/symfony-cmf/vendor/doctrine-phpcr-odm/lib/Doctrine/ODM/PHPCR/UnitOfWork.php:763
/home/david/liip/symfony-cmf/cmf-sandbox/vendor/symfony-cmf/vendor/doctrine-phpcr-odm/lib/Doctrine/ODM/PHPCR/UnitOfWork.php:404
/home/david/liip/symfony-cmf/cmf-sandbox/vendor/symfony-cmf/vendor/doctrine-phpcr-odm/lib/Doctrine/ODM/PHPCR/UnitOfWork.php:386
/home/david/liip/symfony-cmf/cmf-sandbox/vendor/symfony-cmf/vendor/doctrine-phpcr-odm/lib/Doctrine/ODM/PHPCR/DocumentManager.php:312
/home/david/liip/symfony-cmf/cmf-sandbox/vendor/symfony-cmf/vendor/doctrine-phpcr-odm/tests/Doctrine/Tests/ODM/PHPCR/Functional/BasicCrudTest.php:152

[PHPCR-33] ReferenceOne: targetDocument parameter should be optional

Sun, 13 Nov 2011 19:16:57 +0000

the targetDocument describes what class to expect in the reference. as the class is usually determined automatically, this parameter should be optional.

[PHPCR-32] separate the logic to determine the document class for a node

Sun, 13 Nov 2011 19:09:53 +0000

when loading a node from the database, you can either explicitly specify the document class to be used or it is determined programmatically. you can inject your own logic, but the default logic is right in UnitOfWork, and duplicated. this should be moved to a separate class for better reusability.

this would also be a good moment to get rid of phpcr:alias in favor of phpcr:class. we could provide an implementation for the old phpcr:alias as one of the resolvers users can plug in, if somebody really prefers the alias approach.

[PHPCR-31] add support for metadata caching

Wed, 28 Dec 2011 23:28:05 +0000

add support for metadata caching

[PHPCR-30] add support for result caching

Thu, 19 Jul 2012 18:26:54 +0000

add support for result caching

[PHPCR-29] Add support to flush only one document through DocumentManager#flush()

Fri, 3 Feb 2012 09:21:00 +0000

see https://github.com/doctrine/doctrine2/pull/166

[PHPCR-28] figure out proper handling of types in DocumentManager::quote()

Wed, 22 Feb 2012 14:58:03 +0000

figure out proper handling of types in DocumentManager::quote()

[PHPCR-27] adding a generic "node" document

Sat, 22 Oct 2011 13:05:04 +0000

see http://groups.google.com/group/symfony-cmf-devs/browse_thread/thread/914ba1c32d873ed5

[PHPCR-26] Github-PR-56 by uwej711: Fix metadata loading of builtin documents

Sat, 22 Oct 2011 13:04:43 +0000

This issue is created automatically through a Github pull request on behalf of

{username}

Url: https://github.com/doctrine/phpcr-odm/pull/56

Message:

The wrapped metadata driver ensures that metadata for the builtin
documents is loaded. Still the DoctrineAnnotations need to be registered
with the AnnotationRegistry.

see https://github.com/symfony-cmf/cmf-sandbox/issues/20

[PHPCR-25] Github-PR-59 by starkj: Referrers

Fri, 16 Sep 2011 15:07:35 +0000

This issue is created automatically through a Github pull request on behalf of

{username}

Url: https://github.com/doctrine/phpcr-odm/pull/59

Message:

first of all: sry, i screwed up the commit history here again

Well this is support for referrers.
This patch provides the new annotation "Referrers".
By default a property of this type stores all referrers (weak and hard) in a collection.
You can specify the option "referenceType" with the values "weak" and "hard" (or null) to only get the one or the other type of referring documents (or both types)
Then there is the option "filterName". It's value is passed to the method "get(Weak)References". Actually the option passed to "get(Weak)References" is called "name" in the spec. I named it "filterName" here as "name" is already assigned.

[PHPCR-22] find('\Foo\Bar', $path) vs find('Foo\Bar', $path)

Thu, 2 Feb 2012 19:27:41 +0000

I just noticed that we have an issue in our metadata loading in case a document name is prefixed with a backslash when calling find

// fails
$dm->find('\Foo\Bar', $path);

// works
$dm->find('Foo\Bar', $path);

Should the first work as well?

I have traced the issue to the DriverChain

public function loadMetadataForClass($className, ClassMetadata $class)
{
foreach ($this->drivers as $namespace => $driver) {
if (strpos($className, $namespace) === 0)

{ $driver->loadMetadataForClass($className, $class); return; }

}

throw MappingException::classIsNotAValidDocument($className);
}

notice the strpos() does not bother to check if a preceding backslash is in the $className var.

[PHPCR-21] converting any existing docs to reST so that it can be added to the site

Mon, 22 Oct 2012 15:02:10 +0000

PHPCR ODM is listed on the Doctrine website:
http://www.doctrine-project.org/projects/phpcr_odm

build doc in this repository:

https://github.com/doctrine/phpcr-odm-documentation

The next step would be to collect all the various documentation flying around and convert them to reST format:
https://github.com/doctrine/phpcr-odm/wiki/_pages
http://melp.nl/2011/07/symfony2-phpcr-doctrine2-jackalope-recipe/ (needs to be made Symfony2 unspecific)
http://www.craftitonline.com/2011/07/first-symfony2-cmf-based-cms-pagesbundle/ (needs to be made Symfony2 unspecific)
http://cmf.symfony.com/slides.html (needs to be made Symfony2 unspecific)

any other articles flying around?

of course we should also reference PHPCR related docs

[PHPCR-20] Quality assurance and testing

Wed, 28 Dec 2011 23:31:50 +0000

Look at test coverage and write more tests if necessary. Focus on the exposed api functional tests so the changes to share code with mongo db ~~PHPCR-19~~ can be tested.

[PHPCR-19] Code cleanup and refactoring, align to other odm implementations

Sat, 30 Jul 2011 13:03:05 +0000

Refactor the code to share more code with mongodb and other ODM implementations. Can we extract stuff into common base classes or adjust mongo so we can extend from it? The current code is often copy-paste with some small edits all over which makes it hard to update with new features and bugfixes from mongodb.

Also have a look at the OXM - we probably could profit from collaboration there too, as PHPCR is somewhere between document store and XML database. http://www.doctrine-project.org/blog/doctrine-oxm-intro

Implement ObjectManager interface and maybe add to the common interfaces like findMany suitable for us.

[PHPCR-18] Documentation

Wed, 3 Aug 2011 10:02:30 +0000

Create better user documentation. The README is far too long, split it.
Create some documents for the doctrine website and do a doctrine-project.org/projects/phpcr_odm

[PHPCR-17] Id generator and failsafe storage

Sat, 22 Oct 2011 13:04:25 +0000

Have an id generator that can build the path (id) from parent node and node name.
(The current setup with the id being the path leaves it to the user to make sure the parent node exists. You get really non-helpful strange error message if the parent does not exist.)

[PHPCR-16] Annotation for referrers

Fri, 2 Sep 2011 13:11:36 +0000

once reference annotation in ~~PHPCR-10~~ is finished, we should also map the inverse, the list of documents referencing this document. this is a read only property.

[PHPCR-15] Node property mappings

Sat, 22 Oct 2011 13:03:55 +0000

Annotation to map node name to a field (read-only except when creating a document). should be NodeName because NAME is one of the property types.
Align the annotations with the PHPCR\PropertyType types and map all types (missing for example the PATH type).

[PHPCR-14] refactor document class detection

Mon, 8 Aug 2011 11:34:29 +0000

make document class detection strategy injected. this is in Doctrine/ODM/PHPCR/UnitOfWork.php createDocument

the default strategy should do the current behaviour in that method, but use the explicit parameter first if specified before looking at the phpcr:class attribute.

[PHPCR-13] Implement DocumentManager::merge()

Wed, 9 Jan 2013 14:34:17 +0000

Implement DocumentManager::merge()

[PHPCR-12] Use PHPCR\FactoryInterface to bootstrap

Mon, 8 Aug 2011 11:23:37 +0000

The phpcr-odm should use the factory implementations to bootstrap the phpcr implementation, instead of using new Repository (and jackalope transport and whatnot)

[PHPCR-11] Expose transaction API

Sat, 15 Oct 2011 16:13:45 +0000

this requires support in PHPCR/Jackalope

[PHPCR-10] add support for (weak)references

Fri, 16 Sep 2011 15:08:34 +0000

creating and removing references

[PHPCR-9] add logging capabilities

Sat, 30 Jul 2011 15:50:06 +0000

[PHPCR-8] add support for getting node(s) with subnodes at once

Mon, 10 Oct 2011 09:49:59 +0000

this requires support for this in PHPCR/jackalope

[PHPCR-7] add support for "eventual migrations"

Reference — Mon, 8 Oct 2012 07:31:08 +0000

https://doctrine-mongodb-odm.readthedocs.org/en/latest/reference/migrating-schemas.html

[PHPCR-6] add mappings to reference parents in document properties

Sat, 22 Oct 2011 13:05:36 +0000

add mappings to reference parents in document properties

[PHPCR-5] test with Midgard2 PHPCR

Wed, 28 Dec 2011 23:29:48 +0000

https://github.com/bergie/phpcr-midgard2

[PHPCR-4] add mappings to reference versions in document properties

Fri, 3 Feb 2012 08:11:01 +0000

add mappings to reference versions in document properties

[PHPCR-3] add support for lazy loading documents

Fri, 2 Sep 2011 13:09:05 +0000

add support for lazy loading documents

[PHPCR-2] load document with child annotation

Fri, 24 Jun 2011 13:14:55 +0000

if i did not previously load a document of the class of the child, phpcr-odm can not know the alias to load it. it throws an exception.

for example, use $this->documentManager->find('My\Class', '/path/to/document'); where My\Class has an @child annotation for a child that is a File. it has the file alias, but phpcr-odm knows nothing of that alias if i did not previously try to find something with 'Doctrine\...\File' that made it load the meta data.

the workaround is to get the repositories to make phpcr-odm know the alias, but this is no solution.
$this->documentManager->getRepository('Doctrine\ODM\PHPCR\Document\Resource');
$this->documentManager->getRepository('Doctrine\ODM\PHPCR\Document\File');

we could add something to specify the document class in the child annotation, but this sounds stupid.

and getting a document without knowing its document class beforehand would be a nice feature in general. however, the info is currently scattered in annotations over the project. any idea how we could make phpcr-odm know all alias to document class mappings?

[PHPCR-1] children/child annotation add value later

Fri, 22 Jul 2011 07:40:32 +0000

when using the child annotation, it is not possible to assign a child document with a child of its own after persisting the parent document. to reproduce, take the Functional/FileTest.php and change
$parent->file = new File();
$parent->id = '/functional/filetest';
$parent->file->setFileContentFromFilesystem(dirname(_FILE_) .'/_files/foo.txt');

$this->dm->persist($parent);

to
$parent->id = '/functional/filetest';
$this->dm->persist($parent);

$parent->file = new File();
$parent->file->setFileContentFromFilesystem(dirname(_FILE_) .'/_files/foo.txt');

you will get "mandatory child node

{http://www.jcp.org/jcr/1.0}

content does not exist"

[OXM-2] Mapped-superclass, indexes not gathered

Fri, 18 May 2012 12:53:44 +0000

GenericPositionPair XML:
<mapped-superclass name="GenericPositionPair">
<indexes>
<index columns="position" />
</indexes>
<field name="position" type="integer" column="position" />
</mapped-superclass>

GenericPrimaryPositionPair XML:
<mapped-superclass name="GenericPrimaryPositionPair">
<indexes>
<index columns="isPrimary" />
</indexes>
<field name="isPrimary" type="boolean" column="isPrimary" />
</mapped-superclass>

PrimaryPositionPair XML:
<entity name="PrimaryPositionPair" table="PrimaryPositionPair">
<id name="first" type="integer" column="first_id" association-key="true" />
<id name="second" type="integer" column="second_id" association-key="true" />
<many-to-one field="first" target-entity="First">
<join-column name="first_id" referenced-column-name="id" />
</many-to-one>
<many-to-one field="second" target-entity="Second">
<join-column name="second_id" referenced-column-name="id" />
</many-to-one>
</entity>

PHP:
PrimaryPositionPair exteds GenericPrimaryPositionPair
GenericPrimaryPositionPair extends GenericPositionPair

Finally - the resulting SQL statement contains no idexes on position and isPrimary fields.

Suggestion - wouldn't it be easier to just include attribute index="true" instead od <indexes> tag, since attribute unique="true" already works.

[OXM-1] Composite string key ignoring the length attribute

Thu, 29 Mar 2012 15:36:18 +0000

Hello, I have the following XML mapping

And the sql output is:

CREATE TABLE Auth (itemname VARCHAR(255) NOT NULL, userid VARCHAR(255) NOT NULL, bizrule LONGTEXT DEFAULT NULL, data LONGTEXT DEFAULT NULL, PRIMARY KEY(itemname, userid)) ENGINE ...

So, the length atrtibute is always ignored. In MyIsam it breaks the script because of the maximum key limit

[MODM-170] Unique index on embedded document

Wed, 15 May 2013 10:58:29 +0000

Hi,

Bug checked on versions:
doctrine/mongodb-odm (1.0.0-BETA7)
doctrine/mongodb-odm-bundle (v3.0.0-BETA3)
and
doctrine/mongodb-odm (dev-master 6fd7a46)
doctrine/mongodb-odm-bundle (dev-master 23c08a4)

I've created unique index on embedded document and ODM seem not to be working properly. When unique index is violated MongoCursorException is thrown and this behavior is desired.
But, the document sometimes is persisted anyway. Document structure is invalid.

Thrown exception:
mymongoserver.xx:27017: E11000 duplicate key error index: prj.Grid.$boxes_offer_$id_1_boxes_tag_$id_1 dup key: { : ObjectId('51555bbe31bcb2c70e000001'), : "dom" }

Grid document sketch:

{ _id: boxes:[DBref(Offer), DBref(Offer), DBref(Offer)] tag: DBref(Tag) }

unique index on boxes.tag

Any help would be appreciated.

[MODM-169] Filter API is not unified between ODM and ORM

Mon, 10 Dec 2012 14:42:18 +0000

Hi,

I'm implementing some functionality around filters which will ideally work for both ORM and ODM. The API for managing filters is different on `Doctrine\ORM\EntityManager` and `Doctrine\ODM\MongoDB\DocumentManager`, while the CouchDB implementation of ODM has no filter concept.

For example, ORM EntityManager has getFilters(), hasFilters(), while ODM MongoDB DocumentManager has getFilterCollection().

I was wondering what your thoughts were on defining the filter API in an interface, to improve consistency when implementing cross-library functionality?

Thanks,
Craig

[MODM-168] Can't Use Custom Repository Class for Embedded Doc When Using YAML Driver

Sun, 29 Jul 2012 23:42:17 +0000

When using the Yaml driver the ClassMetadata generation process won't create and use the indicated custom repository class for an embedded document. From what I can see digging into the actual code, it will work when using the Annotations or XML drivers, but in the Yaml driver the call to setCustomRepositoryClass is inside of a conditional that only gets entered if the document type is 'document'.

I'm not completely sure, but from what I can see elsewhere in the code, it looks like mapped superclasses should also be able to have a custom repository class, but can't when using the Yaml driver.

So I reckon what would work would be to change the code as indicated below:

<<EXISTING CODE>>
//Doctrine/ODM/MongoDb/Mapping/Driver/YamlDriver.php, line 66
if ($element['type'] == 'document') {
if (isset($element['repositoryClass']))

{ $class->setCustomRepositoryClass($element['repositoryClass']); }

} elseif ($element['type'] === 'mappedSuperclass')

{ $class->isMappedSuperclass = true; }

elseif ($element['type'] === 'embeddedDocument')

{ $class->isEmbeddedDocument = true; }

<<TO THIS>>
if (isset($documentAnnot->repositoryClass))

{ $class->setCustomRepositoryClass($element['repositoryClass']); }

[MODM-167] Undefined index exception when a new document is detatched in onFlush

Wed, 27 Jun 2012 21:36:42 +0000

Undefined index exception when a new document is detatched in onFlush

[MODM-166] recomputeSingleDocumentChangeSet does not work for collections

Wed, 27 Jun 2012 22:04:51 +0000

If you have a document with a collection, during computation of the changeSet before persist a reference to that collection is placed in originalData, not a copy. Therefore, if you change the collection in an onFlush event listener, then call recomputeSingleDocumentChangeSet, the changes to the collection are not recognised, because the originalData has changed also.

I will create a test, and hopefully fix for this soon.

[MODM-165] Identity map doesn't work (tested only with Symfony)

Fri, 20 Apr 2012 23:25:29 +0000

I tested a basic find (by id) query in Symfony and it seems that the identity map feature does not work.
here the code: https://gist.github.com/2431505

4 query with a default Doctrine ODM/Symfony configuration give me 4 query in mongostat.

[MODM-164] DocumentPersister's prepareQuery() method is not suitable for preparing newObj for update queries

Thu, 5 Apr 2012 06:47:40 +0000

Doctrine\ODM\MongoDB\Query\Expr::getNewObj() uses Doctrine\ODM\MongoDB\Persisters\DocumentPersister::prepareQuery() method for preparing newObj. However, prepareQuery is not suitable for that.

The first lines in prepareQuery method should apply to find queries only:

if (is_scalar($query) || $query instanceof \MongoId) {
$query = array('_id' => $query);
}
if ($this->class->hasDiscriminator() && ! isset($query[$this->class->discriminatorField['name']])) {
$discriminatorValues = $this->getClassDiscriminatorValues($this->class);
$query[$this->class->discriminatorField['name']] = array('$in' => $discriminatorValues);
}

Recommendation: DocumentPersister should introduce a new method, such as prepareNewObj($newObj) for preparing the newObj array. Expr::getNewObj() should be change to invoke the new method.

[MODM-163] @ReferenceMany and Inheritance

Thu, 1 Mar 2012 18:07:13 +0000

@ReferenceMany doesn't seem to work when used within a child class unless I specify @InheritanceType("CLASS_PER_COLLECTION") (which is fine b/c that works for our architecture)

Here is an example from our code:

//Parent Class

use Doctrine\Common\Collections\ArrayCollection;

/**

@Document(collection="homepages")
@ChangeTrackingPolicy("DEFERRED_IMPLICIT")
@Indexes({
@Index(keys= {"vertical"="asc","ts"="desc"}
, safe="true"),
@Index(keys= {"ts"="desc"}
, safe="true")
})
*/
class Homepage extends MappedDocument
{

//** References
/**

@ReferenceMany(targetDocument="Post")
@var list<Post>
*/
protected $touts;

}

//Child Class
/**

@Document(collection="readmes")
@ChangeTrackingPolicy("DEFERRED_IMPLICIT")
@Indexes({
@Index(keys= {"vertical"="asc"}
, safe="true")
})
*/
class Readme extends Homepage { //** References /** * @ReferenceMany(targetDocument="Post") * @var list<Post> */ protected $more_touts; }

If I don't add the @InheritanceType annotation the $more_touts data never gets persisted into the DB.
Other types such as @ReferenceOne all work just fine

[MODM-162] Introduction Tutorial,suitable version

Wed, 15 Feb 2012 11:02:37 +0000

HI all,

I am working on a project where I would like to use mongoDB ODM. But while following this tutotorial : http://docs.doctrine-project.org/projects/doctrine-mongodb-odm/en/latest/reference/introduction.html, it appears to me that the download odm library doesn't work with the code: missing code or undefined classes. Therefore I woulld like to know what's the corresponding version mongodb ODM of the tutorial.

Thank's in advance

regards

near

[MODM-161] Bug with index definition

Fri, 15 Jun 2012 08:03:07 +0000

All is there: https://gist.github.com/1682981

[MODM-160] Errors when merging new documents with two levels of embedded documents

Sat, 4 Feb 2012 23:50:33 +0000

There's two different error messages that can be found from this.

If it's EmbedMany in an array (not an ArrayCollection), the following error message results:

Argument 1 passed to Doctrine\ODM\MongoDB\PersistentCollection::__construct() must implement interface Doctrine\Common\Collections\Collection, array given, called in mongodb-odm/lib/Doctrine/ODM/MongoDB/UnitOfWork.php on line 1830 and defined

Otherwise it's:

Undefined index: <blank>

Failing tests have been created and a PR has been submitted on GitHub: https://github.com/doctrine/mongodb-odm/pull/230

[MODM-159] Querying a collection by Embedded objects identifier not working.

Wed, 30 Nov 2011 03:56:14 +0000

Reference objects identifiers are stored as '$id' in database when Embedded objects identifiers are stored as '_id'. When querying a collection by embedded objects identifier, DocumentPersister->prepareQueryValue() converts it to '$id' although it is stored in DB as '_id'. So querying for reference object ids work but embedded objects do not.

DocumentPersister->prepareQueryValue() first checks if field has TargetDocument mapping, if it is true it checks if field is target document's identifier, if this also returns true
it prepares the field as '$id' without looking at if it is Embedded or Reference object ... If TargetDocument it is a Reference object it works since Reference objects identifiers are stored as '$id' but if TargetDocument is Embedded object, query returns empty as theres no field such '$id' in EmbeddedObject, identifier is '_id' instead..

Is this a bug / issue or am i missing something?

[MODM-158] Doctrine\ODM\MongoDB\Mapping\Type\TimestampType should use MongoDate instead of MongoTimestamp

Thu, 24 Nov 2011 18:00:21 +0000

When using the @Timestamp mapping type for a class Doctrine uses MongoTimestamp and it creates very incorrect times in the DB. According to PHP documentation, you should not use MongoTimestamp for creating timestamps, instead MongoDate should be used.

I've attached a patch that changes it to MongoDate and this works splendid when you assign a timestamp to a @Timestamp value

	/**
	 * @Field(type="timestamp")
	 */
	protected $created_on;

	/**
	 * @Field(type="timestamp")
	 */
	protected $updated_on;

	public function __construct($options = NULL)
	{
		$this->created_on = $this->updated_on = time();
		parent::__construct($options);
	}

[MODM-157] Github-PR-151 by l3pp4rd: fixes triggering fatal error on preupdate event in case changeset is clea

Mon, 19 Sep 2011 13:51:24 +0000

This issue is created automatically through a Github pull request on behalf of

{username}

Url: https://github.com/doctrine/mongodb-odm/pull/151

Message:

fixes triggering fatal error on preupdate event in case changeset is cleared during onFlush

similar issue is fixed in ORM it should be supported on ODM mongodb also

[MODM-156] Github-PR-152 by vladar: Property ClassMetadata::file is not serialized

Thu, 25 Aug 2011 18:02:51 +0000

This issue is created automatically through a Github pull request on behalf of

{username}

Url: https://github.com/doctrine/mongodb-odm/pull/152

Message:

This is causing errors, when saving gridfs files with persistent metadata cache engine (like apc, memcached, etc).

I've also found same bug in Jira - http://www.doctrine-project.org/jira/browse/MODM-132 but seems that it is not fixed yet.

Added fix + tests.

[MODM-155] Github-PR-148 by roed: fixed generating of classes

Sun, 21 Aug 2011 14:46:29 +0000

This issue is created automatically through a Github pull request on behalf of

{username}

Url: https://github.com/doctrine/mongodb-odm/pull/148

Message:

fixed the generating of classes based on xml files, changed ClassMetadata to ClassMetadataInfo in these files (as in the ORM tool/mapping)

the following did not work, but works after these changes:
$cmf = new \Doctrine\ODM\MongoDB\Tools\DisconnectedClassMetadataFactory();
$cmf->setDocumentManager($this->_dm);
$cmf->setConfiguration($this->_dm->getConfiguration());
$driver = $this->_dm->getConfiguration()->getMetadataDriverImpl();

$metadatas = $cmf->getAllMetadata(); //this would break it

// $this->_dm is an instance of Doctrine\ODM\MongoDB\DocumentManager

[MODM-154] Github-PR-150 by tecbot: [XMLDriver] fixed an error in hydration classes when the name is not equal to the fieldName

Sun, 21 Aug 2011 14:46:27 +0000

This issue is created automatically through a Github pull request on behalf of

{username}

Url: https://github.com/doctrine/mongodb-odm/pull/150

Message:

[MODM-153] "Near" Query does not work.

Mon, 20 Feb 2012 19:54:57 +0000

"Near" statement does not work for me. The following code returns all cities from collection:

$cities = $this->dm->createQuery('City')
    ->field('coordinates')->near(50, 60)
    ->execute();

Could you please fix it?

[MODM-152] Single Collection Inheritance mapping does NOT work if the subclasses are in a different namespace

Sat, 9 Jul 2011 16:19:34 +0000

I have described the issue in detail here: https://github.com/doctrine/mongodb-odm/issues/124

[MODM-151] Missing Annotation class HasLifecycleCallbacks

Thu, 7 Jul 2011 13:14:42 +0000

Annotation class HasLifecycleCallbacks is missing in Doctrine\ODM\MongoDB\Mapping\Annotations

[MODM-150] XSD file for XML mappings is incomplete

Thu, 7 Jul 2011 12:40:20 +0000

The XSD file for XML mappings (http://www.doctrine-project.org/schemas/odm/doctrine-mongo-mapping.xsd) appears to be incomplete:

Only document is allowed as root tag, not mapped-superclass or embedded-document
The name attribute for the document tag is not allowed according to the XSD file
The fieldName, index and unique attributes for the field tag is not allowed according to the XSD file

These are the problems I discovered at the moment, I haven't yet checked for more problems. The XSD file probably needs a bigger update.

Attached is a patch file that adds the missing attributes, I haven't dug into Doctrine enough to create the mapped-superclass or embedded-document tags.

[MODM-149] Fix PHPDoc @return types in various places

Thu, 5 Apr 2012 14:23:56 +0000

In certain PHPDoc blocks for functions, the @return type is not of the right type. This causes auto-completion issues in various IDEs (I'm using PhpStorm).

For example, in \Doctrine\ODM\MongoDB\DocumentManager on line #341 the ->createQueryBuilder($documentName = null) function.

/**

Create a new Query instance for a class.
*
@param string $documentName The document class name.
@return Document\ODM\MongoDB\Query <--------------------------- MUST BE Query\Builder !
*/
public function createQueryBuilder($documentName = null) { return new Query\Builder($this, $this->cmd, $documentName); }

[MODM-148] Do not add '$db' in reference when referencing document from same $db

Thu, 2 Jun 2011 08:18:53 +0000

When using ReferenceOne or ReferenceMany , doctrine will create fully-qualified reference to the object (with all fields: '$id', '$ref', '$db') even when reference is within same $db.

This approach causes several problems: for example we use mongo database as a template for new clients - when new client registers, template database is copied for him. But since it contains hardcoded $db - copy operation becomes resource consuming, since we have to loop through every document of every collection and fix $db reference.

Also maintenance suffers, since you can't easily rename database when required.

Is it possible to omit $db part when referencing document from same db?

[MODM-147] No possibility to get a json object by a working document with toArray method (inluding all the embedded documents as arrays)

Sat, 28 May 2011 09:13:33 +0000

Description of the problem here:

http://stackoverflow.com/questions/6155189/doctrine-odm-mongodb-get-a-complete-array-of-an-object

Problem with the unincisive toArray() method.

[MODM-146] Doctrine MongoDB ODM load referenced documents ends in an endless loop

Sat, 28 May 2011 08:21:47 +0000

Description of the problem here:

http://stackoverflow.com/questions/6103483/doctrine-mongodb-odm-load-referenced-documents

[MODM-145] QueryBuilder references() to does not support references on embedded objects' fields

Tue, 25 Oct 2011 13:56:55 +0000

I noticed that the references() method does not support fields on embedded objects, as the argument to the preceding field() method will be passed into getFieldMapping() and trigger an exception. I suppose a solution would require multiple calls to getFieldMapping() in order to dive into the embedded object's class metadata.

To demonstrate, below is an example of a UserRepository class. The User document contains an embeddedObject that itself references another User:

class UserRepository extends DocumentRepository
{ 
    public function findByEmbeddedObjectReference(User $user)
    {
        return $this->createQueryBuilder()
            ->field('embeddedObject.user.$id')->equals($user->getId())
//          ->field('embeddedObject.user')->references($user)
            ->getQuery()
            ->execute();
    }
}

Using field()/equals() works fine as an alternative to references(), so there is no urgent need for this feature.

[MODM-144] Bi-Directional References Feature

Wed, 18 May 2011 23:49:19 +0000

I cant´t reproduce the Bi-Directional References with my own example or the example of the documentation.
Perhaps the documentation is not up to date or their ist a bug.

BlogPost.php
<?php

/** @Document */
class BlogPost
{
/** @Id */
public $id;

/** @String */
public $title;

/** @String */
public $content;

/** @String */
public $createtime;

/** @String */
public $updatetime;

/** @ReferenceMany(targetDocument="PostComment", mappedBy="post") */
private $comments;
}

PostComment.php
<?php

/** @Document */
class PostComment
{
/** @Id */
public $id;

/** @String */
public $name;

/** @String */
public $mail;

/** @String */
public $content;

/** @String */
public $createtime;

/** @String */
public $updatetime;

/** @ReferenceOne(targetDocument="BlogPost", inversedBy="comments") */
private $post;
}

CommentController.php
// Save the Post
$post = new BlogPost();
$post->setTitle = 'testtitle';
//$post->content = 'testcontent';
//$post->createdate = time();

$comment1 = new PostComment();
$comment1->title = 'testcommenttitle1';

$comment2 = new PostComment();
$comment2->title = 'testcommenttitle2';

$comment3 = new PostComment();
$comment3->title = 'testcommenttitle3';

$dm->persist($comment1);
$dm->persist($comment2);
$dm->persist($comment3);
$dm->flush();

echo $post->id;

/*$posts = $dm->createQueryBuilder('BlogPost')
->getQuery();*/

$post = $dm->getRepository('BlogPost')->find('4dd45739f563724c23000002');

Zend_Debug::dump($post);
$comments = $post->getComments();

------------------------
In the documentation the example is
$post1->setUser($user);
But the only working for me is:
$post->setTitle = 'testtitle';

Anyway, I can´t get the Comments from the mongodb.
I always get this error.
Fatal error: Call to undefined method BlogPost::getComments()
This is a correct error message because BlogPost really dont have a getComments()
method. How do I get my Comments then?
Any help would be great.

Greetings tronga

[MODM-143] Mismatch in configuration classes, can't enable logging

Mon, 16 May 2011 09:15:23 +0000

My bootstrap:

 
        $config = new Doctrine\ODM\MongoDB\Configuration();
        $config->setProxyDir(APPLICATION_PATH . '/../data/cache');
        $config->setProxyNamespace('Proxies');
        $config->setDefaultDB([skip]);

        $config->setHydratorDir(APPLICATION_PATH . '/../data/cache');
        $config->setHydratorNamespace('Hydrators');

        $config->setLoggerCallable(function(array $log) { print_r($log); });

        $reader = new \Doctrine\Common\Annotations\AnnotationReader();
        $reader->setDefaultAnnotationNamespace('Doctrine\ODM\MongoDB\Mapping\\');
        $config->setMetadataDriverImpl(
            new \Doctrine\ODM\MongoDB\Mapping\Driver\AnnotationDriver($reader, __DIR__ . '/Documents')
        );

        $manager = \Doctrine\ODM\MongoDB\DocumentManager::create(
            new \Doctrine\MongoDB\Connection(),
            $config
        );

And nothing happens

Trace from Doctrine\MongoDB\Configuration::getLoggerCallable():

#0 [skip]/Doctrine/MongoDB/Connection.php(248): Doctrine\MongoDB\Configuration->getLoggerCallable()
#1 [skip]/Doctrine/MongoDB/Connection.php(231): Doctrine\MongoDB\Connection->wrapDatabase(Object(MongoDB))
#2 [skip]/Doctrine/ODM/MongoDB/DocumentManager.php(287): Doctrine\MongoDB\Connection->selectDatabase([skip])
#3 [skip]/Doctrine/ODM/MongoDB/DocumentManager.php(316): Doctrine\ODM\MongoDB\DocumentManager->getDocumentDatabase('BPM\User')
#4 [skip]/Doctrine/ODM/MongoDB/Persisters/DocumentPersister.php(148): Doctrine\ODM\MongoDB\DocumentManager->getDocumentCollection('BPM\User')
#5 [skip]/Doctrine/ODM/MongoDB/UnitOfWork.php(319): Doctrine\ODM\MongoDB\Persisters\DocumentPersister->__construct(Object(Doctrine\ODM\MongoDB\Persisters\PersistenceBuilder), Object(Doctrine\ODM\MongoDB\DocumentManager), Object(Doctrine\Common\EventManager), Object(Doctrine\ODM\MongoDB\UnitOfWork), Object(Doctrine\ODM\MongoDB\Hydrator\HydratorFactory), Object(Doctrine\ODM\MongoDB\Mapping\ClassMetadata), '$')
#6 [skip]/Doctrine/ODM/MongoDB/DocumentRepository.php(115): Doctrine\ODM\MongoDB\UnitOfWork->getDocumentPersister('BPM\User')
#7 [skip]application/library/BPM/UserData.php(43): Doctrine\ODM\MongoDB\DocumentRepository->find('4dc9d0192d91365...')
[skip]

get_class($this) from Doctrine\MongoDB\Configuration::setLoggerCallable() write 'Doctrine\ODM\MongoDB\Configuration' like expected, but in getLoggerCallable() write 'Doctrine\MongoDB\Configuration'

Do you have any ideas about this behaviour?

[MODM-142] DocumentRepository::findBy() not compatible with interface

Sat, 7 May 2011 08:28:22 +0000

I want to get a document repository for my Document\Event document class but instead i get a fatal error.

Pseudo

<?php

use Doctrine\MongoDB\Connection;
use Doctrine\ODM\MongoDB\DocumentManager;
use Doctrine\ODM\MongoDB\Configuration;
use Documents\Event;

$manager = new DocumentManager(
    new Connection(...),
    new Configuration(...)
);

$manager->getRepository('Documents\Event');

Fatal error: Declaration of Doctrine\ODM\MongoDB\DocumentRepository::findBy() must be compatible with that of Doctrine\Common\Persistence\ObjectRepository::findBy() in /home/jpieper/Workspace/Jersey/vendor/doctrine-common/lib/Doctrine/ODM/MongoDB/DocumentRepository.php on line 39

DoctrineCommonPersistenceObjectRepository.php (github@5a285537)

public function findBy(array $criteria, array $orderBy = null, $limit = null, $offset = null);

DoctrineODMMongoDBDocumentRepository.php (github@8d02e843)

public function findBy(array $criteria) { ... }

See https://github.com/doctrine/common/commit/5a2855372834cf37e0408e80dcb9a9c97ec1d352#lib/Doctrine/Common/Persistence

[MODM-141] Doctrine ODM: Documentation error

Tue, 26 Apr 2011 18:38:27 +0000

I think that is a documentation issue, in http://www.doctrine-project.org/docs/mongodb_odm/1.0/en/reference/query-builder-api.html (15.3. Modifier Operations) the queries are like:

$dm->createQueryBuilder('User')

~~>field('password')~~>set('newpassword')

~~>field('username')~~>equals('jwage')

->getQuery()
->execute();

But it is missing the update(), it should be like:

$dm->createQueryBuilder('User')

->update()
~~>field('password')~~>set('newpassword')

~~>field('username')~~>equals('jwage')

->getQuery()
->execute();

All the queries in that section have similar issue

[MODM-140] Issue with nested embdedded documents after adding an EmbeddedDocument to Document

Mon, 19 Dec 2011 02:05:44 +0000

I'm using the latest version of Doctrine ODM (fresh from Git).

I have three levels of Documents (Two embedded); Category -> EmbedsMany: Post -> EmbedsMany PostVersion.

Step-by-step:

1. Make a new Post (Post1), 2 PostVersions (PostVersion1 and 2) and a Category
2. Add Post1 to Category
3. Persist Category, Flush, Clear
4. Retrieve Category
5. Make a new Post (Post2) and 2 PostVersions(PostVersion3 and 4)
6. Add Post2 to Category
7. Flush

If you're following properly, at this stage in the database there should be:
1 Category,
2 Posts
4 PostVersions ... 2 PostVersions in each Post

However, what actually happens is:
1 Category,
2 Posts
4 PostVersions ... 4 PostVersions in Post1, 0 PostVersions in Post2

On StackOverflow: http://bit.ly/ekFbe2
Testcase Gist: https://gist.github.com/920914

A work around is to make Post2 and add it to Category, flush, then make new PostVersions and flush again.

I did some debugging but I don't know enough about the internals to fix the issue.

[MODM-139] [PATCH] @ReferenceMany with no referenceMapping cannot handle DBRef in all / in queries

Fri, 8 Apr 2011 08:08:17 +0000

I have thoose examples :

/** @Document 
 * @InheritanceType("SINGLE_COLLECTION")
 * @DiscriminatorField(fieldName="type")
 * @DiscriminatorMap({"Test\Product"="Product", "Test\Year"="Year"})
*/
Attributes {
   /** @Id */
   protected $_id;
}

/** @Document */
class Product extends Attributes {}

/** @Document */
class Year extends Attributes {}

/**
 * Classe de base pour les différents contenus
 * @Document
 * @InheritanceType("SINGLE_COLLECTION")
 * @DiscriminatorField(fieldName="type")
 * @DiscriminatorMap({"Test\Document"="Document", "Test\Infos"="Infos"})  
 */
class Content
{
   /** protected $_id */
    /** @ReferenceMany */
    protected $_attributes;
}

And the querying stuff

//and the query : 
$queryBuilder = $dm->createQueryBuilder('Test\DOcument');
//...
$attribute1Ref = $dm->createDBRef($attribute1Object);
$attribute2Ref = $dm->createDBRef($attribute2Object);
$queryBuilder->field('_attributes')->all(array($attribute1Ref, $attribute2Ref));
$queryBuilder->getQuery()->execute();//Won't work as the generated query won't specify the "_doctrine_class_name" value.

Proposed patch in DocumentManager :

    /**
     * Returns a DBRef array for the supplied document.
     *
     * @param mixed $document A document object
     * @param array $referenceMapping Mapping for the field the references the document
     *
     * @return array A DBRef array
     */
    public function createDBRef($document, array $referenceMapping = null)
    {
        $className = get_class($document);
        $class = $this->getClassMetadata($className);
        $id = $this->unitOfWork->getDocumentIdentifier($document);

        $dbRef = array(
            $this->cmd . 'ref' => $class->getCollection(),
            $this->cmd . 'id'  => $class->getDatabaseIdentifierValue($id),
            $this->cmd . 'db'  => $this->getDocumentDatabase($className)->getName()
        );

        // add a discriminator value if the referenced document is not mapped explicitely to a targetDocument
        if ($referenceMapping && ! isset($referenceMapping['targetDocument'])) {
            $discriminatorField = isset($referenceMapping['discriminatorField']) ? $referenceMapping['discriminatorField'] : '_doctrine_class_name';
            $discriminatorValue = isset($referenceMapping['discriminatorMap']) ? array_search($class->getName(), $referenceMapping['discriminatorMap']) : $class->getName();
            $dbRef[$discriminatorField] = $discriminatorValue;
+        }  elseif ($referenceMapping === null) {
+            $dbRef['_doctrine_class_name'] = $class->getName();
+        }
        return $dbRef;
    }

[MODM-138] Field's name attribute does not work for the update queries

Thu, 7 Apr 2011 12:38:04 +0000

Documents

class Test 
{
.
.
.
/**
 * @EmbedOne(targetDocument="Location", name="l")
*/
private $location;
.
.
.
}

/** @EmbeddedDocument */
class Location
{
    /**
	 * @Field(type="float", name="y")
	 */
    public $lat;

    /**
	 * @Field(type="float", name="x")
	 */
    public $lng;

	public function __construct($latitude,$longitude) {
		$this->lat = $latitude;
		$this->lng = $longitude;
	}
}

Update query:

$dm->createQueryBuilder('Test')
->update()
->field('id')->equals(123)
->field('l')->set(new Location(39, 32);
->getQuery(array('upsert' => true))
->execute();

Result of this query is

"l": {
    "lat": 39,
    "lng": 32
},

however, it should be

"l": {
    "y": 39,
    "x": 32
},

also field function can support field name of the class on update queries, as follows

$dm->createQueryBuilder('Test')
->update()
->field('id')->equals(123)
->field('location')->set(new Location(39, 32);
->getQuery(array('upsert' => true))
->execute();

[MODM-137] Undefined index 'criteria' in DocumentPersister

Mon, 4 Apr 2011 18:50:06 +0000

On the master branch, a notice is thrown on line 531 of the DocumentPersister for an undefined index 'criteria'. This is when using the Yaml driver.

https://github.com/doctrine/mongodb-odm/blob/master/lib/Doctrine/ODM/MongoDB/Persisters/DocumentPersister.php#L531

Full notice:
Notice: Undefined index: criteria in /Doctrine/ODM/MongoDB/Persisters/DocumentPersister.php on line 531
PHP Warning: array_merge(): Argument #2 is not an array in /Doctrine/ODM/MongoDB/Persisters/DocumentPersister.php on line 532

Warning: array_merge(): Argument #2 is not an array in /Doctrine/ODM/MongoDB/Persisters/DocumentPersister.php on line 532
PHP Catchable fatal error: Argument 1 passed to Doctrine\MongoDB\Collection::find() must be an array, null given, called in Doctrine/ODM/MongoDB/Persisters/DocumentPersister.php on line 533 and defined in Doctrine/MongoDB/Collection.php on line 169

Catchable fatal error: Argument 1 passed to Doctrine\MongoDB\Collection::find() must be an array, null given, called in Doctrine/ODM/MongoDB/Persisters/DocumentPersister.php on line 533 and defined in /Doctrine/MongoDB/Collection.php on line 169

[MODM-136] Document's fields names are not properly converted to database names in a query

Sun, 27 Mar 2011 09:13:03 +0000

Mappings:

/**
 * @Field(type="date", name="scheduled_at")
 */
private $scheduledAt;

/**
 * @Field(type="date", name="completed_at")
 */
private $completedAt;

Query:

$qb->field('scheduledAt')->lte($now)
   ->addOr($qb->expr()->field('completedAt')->lte($now))
   ->addOr($qb->expr()->field('completedAt')->equals(null))
   ->sort('scheduledAt', 'asc');

Expected result:

db.foo.find({
    "scheduled_at": { "$lte": new Date(...) }, 
    "$or": [ 
        { "completed_at": {  "$lte": new Date(...) } }, 
        { "completed_at": null } ] 
})
.sort({ "scheduled_at": 1 });

Actual result:

db.foo.find({
    "scheduled_at": { "$lte": new Date(...) }, 
    "$or": [ 
        { "completedAt": {  "$lte": new Date(...) } }, 
        { "completedAt": null } ] 
})
.sort({ "scheduledAt": 1 });

[MODM-135] [Cursor] ReferenceMany sort mapping not working

Sat, 26 Mar 2011 07:58:32 +0000

I have a document like this:

/** @Document */
class Page
{
/** @Id */
protected $id;

/** @ReferenceMany(sort=

{"order"="asc"}

) */
protected $blocks;
}

If i have well understood things, i can do:

$blocks = $dm->getRepository('Page')~~>find($id)~~>getBlocks();

blocks should now be sorted by $order property.

This behaviour doesn't seems to work (or maybe i'm missing something).
In the attachment there's a test case

i made the priority major because in my case i haven't found a workaround (i'm using nested referenceMany, a child can have children, which can have children, ..).

[MODM-134] Reference added twice

Fri, 25 Mar 2011 12:55:17 +0000

I have a listener who listens on onFlush event,
i have a document and change a property (integer) in it and call $uow->recomputeSingleDocumentChangeSet().
The result is that all references are added twice.

If i remove the call to $uow->recomputeSingleDocumentChangeSet() all is fine.

Here's my document (notice references added twice on children property):

array (
'children' =>
array (
0 =>
array (
'$ref' => 'block',
'$id' => new MongoId("4d8b663638b6180803000005"),
'$db' => 'app_jules',
'_doctrine_class_name' => 'Design\\PageBundle\\Document
StrategyBlock',
),
1 =>
array (
'$ref' => 'block',
'$id' => new MongoId("4d8b663638b6180803000005"),
'$db' => 'app_jules',
'_doctrine_class_name' => 'Design\\PageBundle\\Document
StrategyBlock',
)
),
'order' => 0,
'parent' =>
array (
'$ref' => 'block',
'$id' => new MongoId("4d8b663638b6180803000003"),
'$db' => 'app_jules',
'_doctrine_class_name' => 'Design\\PageBundle\\Document
ContainerBlock',
),
'type' => 'container',
)

EDIT: if i clear() the $children ArrayCollection before calling $uow->recomputeSingleDocumentChangeSet() all is fine

I tried to reproduce it in a test-case but the result wasn't successful

[MODM-133] array keys with dots aren't persisted for Hash field

Mon, 11 Apr 2011 18:50:50 +0000

array keys with dots aren't persisted for Hash field

in the attachment you will find a complete testcase.

thanks.

EDIT: use the second attachment

[MODM-132] Doctrine\ODM\MongoDB\Mapping\ClassMetaData is loosing "file" property after serialization

Fri, 18 Mar 2011 12:40:12 +0000

After ClassMetaData is awakened it looses the "file" property and that breaks our File model.
File::count() returns 0

I dumped ClassMetaData object with caching enabled and disabled. Here's the diff:

146c146
< [file] =>
—
> [file] => file
149a150,180
> [0] => Array
> (
> [keys] => Array
> (
> [uploaded_at] => 1
> )
>
> [options] => Array
> (
> [safe] => true
> [unique] =>
> )
>
> )
>

The first line is the missing file value. The second block appears to be missing indexes but I'm guessing this information should not be serialized.

[MODM-131] Notice in Doctrine\MongoDB\GridFS::doInsert

Wed, 9 Mar 2011 14:14:59 +0000

Notice: Undefined variable: file in /projects/tbi/vendors/doctrine/odm/lib/vendor/doctrine-mongodb/lib/Doctrine/MongoDB/GridFS.php on line 112

[MODM-130] @ChangeTrackingPolicy notation is ignored in @MappedSuperclass

Wed, 2 Mar 2011 10:56:24 +0000

I am not sure if it's supposed to be that @MappedSuperclass document can define @ChangeTrackingPolicy for multiple documents but in fact it does not work.

In other words in the case below:
===================================================

/**

@MappedSuperclass
@InheritanceType("COLLECTION_PER_CLASS")
@ChangeTrackingPolicy("DEFERRED_EXPLICIT")
*/
abstract class MappedDocument
{
}

/**

@Document(collection="chart")
*/
class Chart extends MappedDocument
{
}

===================================================

class Chart

has InheritanceType = INHERITANCE_TYPE_COLLECTION_PER_CLASS which is expected
but ChangeTrackingPolicy = CHANGETRACKING_DEFERRED_IMPLICIT (value by default) which is NOT expected.

At the same time if to define ChangeTrackingPolicy in the Chart class instead of MappedDocument it works as expected.

[MODM-129] Storing embeded documents containing embeded documents, already persistet in another collection fails

Fri, 25 Feb 2011 11:39:02 +0000

We persist a document a1 containing an embedded document a1.1 which itself contains another embedded document a1.1.1. When the embedded document a1.1 is moved to another document of another collection b1 and needs to get persisted as embedded document b1.1 the embedded document a1.1.1 (which is now part of b1.1, too) is not saved as an embedded document of b1.1.

Example: We use a version object which contains a pageversion as an embedded document. This page object contains multiple elements (stored as embedded documents) which themselves contain several parameter objects (stored as embedded document of elements). Now assume we have such a persisted version and want to "copy" the pageversion in another collection. So we generate a new page object, and add to this page all elements of the persisted pageversion. If we now persist this page, the representation in mongodb contains all elements but not any parameters, which should be part of the page as well (as they are part of an element).

[MODM-128] Upserts in Query builder

Wed, 23 Feb 2011 23:31:45 +0000

It seems that if you just call upsert(true) in a update request, it won't be enough. You have to calm getQuery(array('upsert' => true)) as well in order to have the 'insert if not exist' working.

[MODM-127] Update queries : update() required ?

Wed, 23 Feb 2011 00:04:26 +0000

In the documentation exemples for update queries :
http://www.doctrine-project.org/docs/mongodb_odm/1.0/en/reference/query-builder-api.html#update-queries

it doesn't mention a update() function call any more in update queries.

Did I miss something?

[MODM-126] lessThanOrEq() renamed in lte()

Tue, 22 Feb 2011 23:27:07 +0000

The lessThanOrEq() function referenced in the documentation does not exist ay more, it was replaced by lte().

http://www.doctrine-project.org/docs/mongodb_odm/1.0/en/reference/query-builder-api.html

[MODM-125] Doctrine\ODM\MongoDB\MongoCollection::findOne does not invoke postFindOne event handlers doing query against MongoGridFS collection

Fri, 4 Mar 2011 10:44:12 +0000

subj

it happens because the code goes out of the function at line 334 in file
\Doctrine\ODM\MongoDB\MongoCollection.php
without invoking appropriate event handlers

thanks!

[MODM-124] ClassMetadata shouldn't store defaultDb value

Fri, 4 Mar 2011 10:56:01 +0000

Currently if document doesn't have "db" mapping, it is taken from defaultDb configuration and assigned to classmetadata (in ClassMetadataFactory).

But if we have two documentManagers with different defaultDb configuration, second manager's configuration will be ignored, because "db" value is already set in classMetadata (when the 1st manager was created).

It gets worse with metadata caching, as defaultDb setting is only taken in account when metadata is stored in cache.

This affects a common use-case, when each customer has his own database and defaultDb is defined at runtime.

[MODM-123] Single Collection Inheritance : hydration won't work properly

Wed, 23 Feb 2011 23:46:37 +0000

There is still a problem with Single Collection Inheritance.

Please consider the following code :

 
/**
 * @Document(db="forum", collection="Items")
 * @InheritanceType("SINGLE_COLLECTION")
 * @DiscriminatorField(fieldName="type")
 * @DiscriminatorMap({0="Items", 1="Stuffs"})
*/
class Items
{
    /**
     *
     * @id
     */
    public $id;

    /**
     * @String
     */
    public $title;
}



/**
 * @Document(db="forum", collection="Items")
*/
class Stuffs extends Items
{
    
    /**
     *
     * @id
     */
    public $id;

    /**
     * @String
     */
    public $stuffname;

}

$a = new Stuffs();
$a->stuffname = 'TTT';
$dm->persist($a);
$dm->flush();

Resulting in the database with :

 
{
   "_id": ObjectId("4d5dd082b53251b84e000000"),
   "stuffname": "TTT",
   "type": 1 
}

Now if I do :

 
$result = $dm->find('Items', $a->id);

then $result is an instance of Stuffs

But if I try :

 
$result = $dm->find('Items', '4d5dd082b53251b84e000000');

then $result is an instance of Items

Note that '$a->id' is a string, the same string containing '4d5dd082b53251b84e000000', so :

 
$result = $dm->find('Items', $a->id); 
$result = $dm->find('Items', '4d5dd082b53251b84e000000');

are semantically equivalent. It seems however that hydration would ignore the DiscriminatorMap in the second example.

However If you do :

 
$result = $dm->find('Stuffs', '4d5dd082b53251b84e000000');

You'll get a Stuffs as a result.

Now I tried to find a workaround when you don't know the type of the returned object. My initial intention was to first fetch a document with :

 
$result = $dm->find('Items', '4d5dd082b53251b84e000000');

Then I'm testing a property in the objet to see if it's a Stuffs, if it is, I tried an new :

 
$result = $dm->find('Stuffs', '4d5dd082b53251b84e000000');

In order to fetch a Stuffs. But ... I still get a *Items"!

So basically, if you do :

 
$result = $dm->find('Stuffs', '4d5dd082b53251b84e000000');

You get a Stuffs. But if you do :

 
$dm->find('Items', '4d5dd082b53251b84e000000'); 
$result = $dm->find('Stuffs', '4d5dd082b53251b84e000000');

You get a Items!

[MODM-122] array_slice fails on ReferenceMany and EmbeddedMany fields

Thu, 17 Feb 2011 19:39:40 +0000

I am not sure if it's a bug of the framework or a bug in implementation of array_slice function in PHP
but when I try to pass @ReferenceMany field value into array_slice built-in PHP function it fails with error:

==============================================
array_slice() expects parameter 1 to be array, object given
==============================================

I know that PersistentCollection has method "slice" (at least in master branch) but my concern is backward compatibility with the code which treats ReferenceMany type fields as arrays.
The old code works perfectly until it uses array_slice.

Please let me know are there any workarounds for this or probably you guys are going to implement some fix?

Thanks a lot!

[MODM-121] a call of unknown method "setIdentifierValues" in UnitOfWork class

Wed, 16 Feb 2011 19:17:56 +0000

On DocumentManager::merge() the following error happens:

Fatal error: Call to undefined method Doctrine\ODM\MongoDB\Mapping\ClassMetadata::setIdentifierValues() in /projects/tbi_doctrine/vendors/doctrine/odm/lib/Doctrine/ODM/MongoDB/UnitOfWork.php on line 1378

[MODM-120] [Configuration] problem with changing the defaultDB

Wed, 16 Feb 2011 16:58:15 +0000

What i want to do is to change the database name of the document manager:

$config = new Configuration();
$dm = new DocumentManager($conn, 'my_db', $config);

$config->setDefaultDB('another_db');
$dm->getDatabase(); // 'my_db' insteadof 'another_db'

Is there another solution to do this ?

[MODM-119] "strategy" property in @Field annotation is not recognized

Fri, 11 Feb 2011 13:25:29 +0000

@Collection(strategy="set")
works fine

but
==========================================

@Field(type="collection", strategy="set")
causes error:
Fatal error: Uncaught exception 'BadMethodCallException' with message 'Unknown property 'strategy' on annotation 'Doctrine\ODM\MongoDB\Mapping\Field'.' in /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/Annotation.php on line 77

BadMethodCallException: Unknown property 'strategy' on annotation 'Doctrine\ODM\MongoDB\Mapping\Field'. in /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/Annotation.php on line 77

Call Stack:
0.0007 691072 1.

{main}

() /projects/tbi_doctrine/lab/doctrine/insert.php:0
0.0808 6313168 2. Doctrine\ODM\MongoDB\DocumentManager->persist() /projects/tbi_doctrine/lab/doctrine/insert.php:34
0.0809 6313168 3. Doctrine\ODM\MongoDB\UnitOfWork->persist() /projects/tbi_doctrine/vendors/doctrine/odm/lib/Doctrine/ODM/MongoDB/DocumentManager.php:338
0.0809 6313248 4. Doctrine\ODM\MongoDB\DocumentManager->getClassMetadata() /projects/tbi_doctrine/vendors/doctrine/odm/lib/Doctrine/ODM/MongoDB/UnitOfWork.php:1177
0.0809 6313248 5. Doctrine\ODM\MongoDB\Mapping\ClassMetadataFactory->getMetadataFor() /projects/tbi_doctrine/vendors/doctrine/odm/lib/Doctrine/ODM/MongoDB/DocumentManager.php:250
0.0809 6313248 6. Doctrine\ODM\MongoDB\Mapping\ClassMetadataFactory->loadMetadata() /projects/tbi_doctrine/vendors/doctrine/odm/lib/Doctrine/ODM/MongoDB/Mapping/ClassMetadataFactory.php:165
0.0957 6734784 7. Doctrine\ODM\MongoDB\Mapping\Driver\AnnotationDriver->loadMetadataForClass() /projects/tbi_doctrine/vendors/doctrine/odm/lib/Doctrine/ODM/MongoDB/Mapping/ClassMetadataFactory.php:221
0.0978 6669016 8. Doctrine\Common\Annotations\AnnotationReader->getPropertyAnnotation() /projects/tbi_doctrine/vendors/doctrine/odm/lib/Doctrine/ODM/MongoDB/Mapping/Driver/AnnotationDriver.php:182
0.0978 6669016 9. Doctrine\Common\Annotations\AnnotationReader->getPropertyAnnotations() /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/AnnotationReader.php:216
0.0979 6669392 10. Doctrine\Common\Annotations\Parser->parse() /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/AnnotationReader.php:201
0.0983 6678712 11. Doctrine\Common\Annotations\Parser->Annotations() /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/Parser.php:209
0.0983 6678928 12. Doctrine\Common\Annotations\Parser->Annotation() /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/Parser.php:270
0.0986 6680200 13. Doctrine\Common\Annotations\Parser->newAnnotation() /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/Parser.php:349
0.0986 6680840 14. Doctrine\Common\Annotations\Annotation->__construct() /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/Parser.php:536
0.0986 6681624 15. Doctrine\Common\Annotations\Annotation->__set() /projects/tbi_doctrine/vendors/doctrine/common/lib/Doctrine/Common/Annotations/Annotation.php:0

[MODM-118] rename "load" method in Proxy object to "load"

Reference — Fri, 11 Feb 2011 13:33:17 +0000

It would be really great if the method "load" is renamed to something more protected like "__load" or "_doctrineOdmLoad" like it has done for public properties
public $__dm;
public $__identifier;
public $_isInitialized_ = false;

Because otherwise if a referenced document has the same method "load" it causes error like this

"Fatal error: Cannot redeclare Proxies\ProjectProxy::load() in /projects/tbi_doctrine/tmp/doctrine/proxies/ProjectProxy.php on line 46"

[MODM-117] "name" attribute in @Field annotation

Fri, 11 Feb 2011 13:56:39 +0000

It looks like that "name" attribute is not supported anymore in @Field annotation

http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/reference/annotations-reference/en#ann_field
> name - By default the property name is used for the mongodb field name also, however the 'name' attribute allows you to specify the field name.

For instance the code below produces a document inside "mydocs" collection which has only one property "first_name" instead of two:

/** @Document(collection="mydocs") */
class MyDocument
{
/** @Id */
public $id;

/** @Field(type="string") */
public $first_name;

/** @Field(type="string", name="last_name") */
protected $_last_name;

public function __get($propertyName)
{
return $this->

{'_'.$propertyName};
}

public function __set($propertyName, $propertyValue)
{
$this->{'_'.$propertyName}

= $propertyValue;
}
}

$doc = new MyDocument();
$doc->first_name = 'aaa';
$doc->last_name = 'bbb';
dm()->persist($doc);
dm()->flush();

[MODM-116] Collection Per Class Inheritance : Documents of a child class referenced in a parent class may be saved to the parent collection

Thu, 21 Apr 2011 17:13:51 +0000

Here is my class hierarchy (classes & attributes renamed for a better understanding) :

 
/** @Document @InheritanceType("COLLECTION_PER_CLASS") **/
class Parent {
    /** @ReferenceOne(targetDocument="Child") **/
    protected $child;
}

/** @Document **/
class Child extends Parent {
}

When doing :

$parent->setXXX($value);
$parent->getChild()->setXXX($value2)

the $parent->getChild() document is saved to the Parent collection.

It looks like the problems lies in UnitOfWork::executeUpdates :

 
if (get_class($document) == $className || $document instanceof Proxy && $document instanceof $className) {

$child_document is an instance of Proxy (ChildProxy) and also an instance of Parent => saved using the Parent persister.

Shouldn't the test be : get_class($document) == $className || get_class($document) == $className_of_Proxy ?

As a side note : why "if ($class->isEmbeddedDocument)

{ continue; }

" is within the foreach and not a "if ($class->isEmbeddedDocument)

{ return; }

" at the beginning of the method ?

[MODM-115] Persisting a document which references another document drops ID

Thu, 3 Feb 2011 15:54:42 +0000

I have two documents:

@Document
class A {
/** @Id */
public $id;
/** @ReferenceOne */
public $b;
}

@Document
class B {
/** @Id */
public $id;
}

I have an already persisted instance of B, which A references,
though while persisting A and examining the resulting collection the id of B is missing.

{
_id: '000123',
b: {
$db: 'mydb',
$id: '',
$ref: 'b'
}
}

I debugged the code and found the error occurs in DocumentPersister.php at line 210 in the latest git version as of this posting.
The code is:

$inserts[$oid] = $data;

where $data is:

array(
_id => MongoId(000123),
b => array(
$ref => 'b',
$id => MongoID(123000),
$db => 'mydb'
)
)

and $inserts[$oid] becomes:

array(
$oid = array(
_id => MongoId(000123),
b => array(
$ref => 'b',
$id => MongoID(),
$db => 'mydb'
)
)
)

This assignment makes the MongoID disappear somehow!!?

Can't figure it out, could this be a problem with PHP itself?

[MODM-114] wrong method call in Cursor class

Fri, 11 Feb 2011 14:30:12 +0000

i have found a bug in the Cursor class in mongodb-odm:

https://github.com/doctrine/mongodb-odm/blob/master/lib/Doctrine/ODM/MongoDB/Cursor.php#L85 this musst call the current function in the parent class, otherwise mistakes happen when there is a grid fs collection.

[MODM-113] No options for update queries ?

Fri, 11 Feb 2011 14:32:07 +0000

$options are not used for update queries

=> how can we do an update(

{'multiple' => true}

) ?

 
diff -rup doctrine-mongodb-odm-a0667bb/lib/vendor/doctrine-mongodb/lib/Doctrine/MongoDB/Query/Query.php mongodb_odm/lib/vendor/doctrine-mongodb/lib/Doctrine/MongoDB/Query/Query.php
--- doctrine-mongodb-odm-a0667bb/lib/vendor/doctrine-mongodb/lib/Doctrine/MongoDB/Query/Query.php	2011-01-17 06:38:18.000000000 +0100
+++ mongodb_odm/lib/vendor/doctrine-mongodb/lib/Doctrine/MongoDB/Query/Query.php	2011-01-31 17:34:04.000000000 +0100
@@ -172,7 +172,7 @@ class Query implements IteratorAggregate
                 return $this->collection->insert($this->query['newObj']);
 
             case self::TYPE_UPDATE:
-                return $this->collection->update($this->query['query'], $this->query['newObj']);
+                return $this->collection->update($this->query['query'], $this->query['newObj'], $this->options);
 
             case self::TYPE_REMOVE:
                 return $this->collection->remove($this->query['query'], $this->options);

[MODM-112] [PATCH] Allow Hydrator classes to be regenerated only if they are absent

Fri, 11 Feb 2011 14:52:32 +0000

Hydrator classes are either never generated ou regenerated on each request.

The patch add another case : regenerate only if absent.

HydratorFactory::$autoGenerate switches to int and can have 3 values : HydratorFactory::AUTOGENERATE_NEVER, HydratorFactory::AUTOGENERATE_ALWAYS or HydratorFactory::AUTOGENERATE_ABSENT

[MODM-111] Trouble with MappedSuperclass/Single collection inheritance and commit 2e8071a4dc68b027f969

Fri, 11 Feb 2011 14:55:30 +0000

I have the following classes :

@MappedSuperClass
@InheritanceType("SINGLE_COLLECTION")
@DiscriminatorField(fieldName="_class")
@DiscriminatorMap(

{"SuperClass"="SuperClass", "SubClass1"="SubClass1", "SubClass2"="SubClass2"}

)
abstract class SuperClass {}

@Document
class SubClass1 extends SuperClass {}

@MappedSuperClass
abstract class SuperClass2 extends SuperClass {}

@Document
abstract class SubClass2 extends SuperClass2 {}

SubClass2 does not use the single collection.
SubClass1 and SubClass2 do not use the discriminator map.

This broke after commit 2e8071a4dc68b027f969.

Why can't we use MappedSuperclasses in an single collection inheritance strategy ?

[MODM-110] QueryBuilder missing values and values with wrong data types being inserted

Sat, 19 Feb 2011 18:28:25 +0000

Hello,

I'm using annotation mapping for my documents and found something strange when i insert a document (having an embed document) using the query builder...

When i use the document class and persist it, things are fine:

$testCase = new \Documents\Test();
$testCase->testInt = '0';
$testCase->intfields = new \Documents\Embed\Intfields();
$testCase->intfields->intone = '1';
$testCase->intfields->inttwo = '2';
$dm->persist($testCase);
$dm->flush();

Result:
{
"_id": ObjectId("4d417fb1723014d009000008"),
"testInt": 0,
"intfields":

{ "intone": 1, "inttwo": 2 }

}

But when i use the query builder:

$dm->createQueryBuilder()
->insert('Documents\Test')
->field('testInt')->set('0')
->field('intfields.intone')->set('1')
->field('intfields.inttwo')->set('2')
->getQuery()->execute();

Result:
{
"_id": ObjectId("4d417fb1723014d009000009"),
"testInt": "0",
"intfields":

{ "inttwo": "2" }

}

Intone is missing and the values are all string values.

It seems to be a bug, but as i'm new to the doctrine and mongo world, it's more than possible to be a user error. :}

I was using the clone version of the master git hub.. is that beta2?

Regards
S.

PS.: Php files are attached

[MODM-109] Reference with Inheritance: Proxy error: 'document with identifier .. could not be found'

Fri, 11 Feb 2011 15:26:37 +0000

It's hard to explain this issue,

I have a single table Inheritance, the base class is Block. ContainerBlock is a child class of Block.
I have a document Page who have a one-one with ContainerBlock (child of Block). ContainerBlock as many Block.

Test script:
----------------

I have created a complete test-case (see attachment).
phpunit InheritanceReference/InheritanceReferenceTest.php

Expected result:
-----------------------

no error, no exception.

Actual result:
-------------------

1) InheritanceReference\InheritanceReferenceTest::testMulipleInheritance
Doctrine\ODM\MongoDB\MongoDBException: The "Proxy\DocumentBlockProxy" document with identifier "4d3d08116aba269508000001" could not be found.

src/vendor/symfony/vendor/doctrine-mongodb-odm/lib/Doctrine/ODM/MongoDB/MongoDBException.php:69
src/Bundle/InheritanceReference/Proxy/DocumentBlockProxy.php:25
src/Bundle/InheritanceReference/Proxy/DocumentBlockProxy.php:34
src/Bundle/InheritanceReference/InheritanceReferenceTest.php:65

[MODM-108] Random hydratation problem

Tue, 25 Jan 2011 19:01:06 +0000

I have the following collection named Isboo_Item :

{
"_id": ObjectId("4d3d02fec9fa877d44a36978"),
"author": null,
"backpack": null,
"itemType": 1,
"owner": "4d3cf450b532519765080000",
"place": null,
"quality": null,
"quantity": 1,
"value": null
}

I have a such PHP class :

/**

@Document(db="Isboona", collection="Isboo_Item")
*/
class Isboo_Item extends Isboo_Db
{
(...)

When I'm trying :
$dm->findOne($collection, array('_id' => $id));

I get :

Fatal error: Uncaught exception 'ReflectionException' with message 'Class 4 does not exist' in /users/developpement/www/library/Doctrine/ODM/MongoDB/Mapping/ClassMetadata.php:285

However the same works fine with another collection :

{
"_id": ObjectId("4d3cf450b532519765080000"),
"characs":

{ "mana": 64, "strenght": 83, "agility": 69, "dexterity": 88, "constitution": 94, "culture": 79, "vivacity": 57, "eloquence": 64, "intellect": 74, "willpower": 88, "empathy": 96, "charisma": 83 }

,
"name": "Krok",
"position":

{ "IDplace": 0, "posX": 0, "posY": 0, "posLocalX": 0, "posLocalY": 0 }

,
"refFather":

{ "$ref": "Isboo_Character", "$id": ObjectId("4d3cf450b532519765090000"), "$db": "Isboona" }

,
"refMother":

{ "$ref": "Isboo_Character", "$id": ObjectId("4d3cf450b5325197650a0000"), "$db": "Isboona" }

}

[MODM-107] Document Manager does not delete References

Fri, 11 Feb 2011 15:38:41 +0000

References are not deleted when the function $dm->remove($x) is called.
It deltes $x from the database but all references are still persisted.

See function: testManyDeleteReference() in attached file.

[MODM-106] $in fails on document identifiers

Fri, 11 Feb 2011 15:53:18 +0000

If I try to select a couple of documents with the in() query, I receive an empty result set when the selected field is the document id.

The following code works fine and selects the right document:

       $query = $dm->createQueryBuilder("Object\Does\Not\Matter")
                   ->field("id")->equals("4d1db8ba2d8aa162300a0000")
                   ->getQuery()->execute();

Whereas the following query returns nothing:

       $query = $dm->createQueryBuilder("Object\Does\Not\Matter")
                   ->field("id")->in(array("4d1db8ba2d8aa162300a0000"))
                   ->getQuery()->execute();

[MODM-105] inversedBy as ORM

Fri, 4 Mar 2011 10:33:47 +0000

A way to specify "inversedBy" when mapping referenceOne and referenceMany as the ORM have it.

[MODM-104] Creating mongo configuration class instance hangs php

Fri, 11 Feb 2011 15:55:33 +0000

After pasting down the doc tutorial example I've noticed that php hangs on
Configuration instance creation.

require 'Doctrine/Common/ClassLoader.php';
use Doctrine\Common\ClassLoader,
Doctrine\Common\Annotations\AnnotationReader,
Doctrine\ODM\MongoDB\DocumentManager,
Doctrine\ODM\MongoDB\Mongo,
Doctrine\ODM\MongoDB\Configuration,
Doctrine\ODM\MongoDB\Mapping\Driver\AnnotationDriver;
// ODM Classes
$classLoader = new ClassLoader('Doctrine\ODM', 'mongodb_odm/lib');
$classLoader->register();
// Common Classes
$classLoader = new ClassLoader('Doctrine\Common', 'mongodb_odm/lib/vendor/doctrine-common/lib');
$classLoader->register();
// Document classes
$classLoader = new ClassLoader('Documents', _DIR_);
$classLoader->register();

//-------hangs here
$config = new Configuration();

//tried explicit too
// new Doctrine\ODM\MongoDB\Configuration();

No errors or warnigs of any kind generated.

[MODM-103] @File tag support in xml notation

Mon, 20 Dec 2010 16:08:30 +0000

Please correct me if I'm wrong but it looks like that @File tag (Mongo GridFS indicator) is not supported by xmlDriver.
I could not find anything about this feature neither in unitests for the system nor in documentation (as concerning the code probably I missed something but I also could not find anything related to GrisFS in xmlDriver code) .

[MODM-102] Documents which belong to global namespace can not be handled?

Fri, 11 Feb 2011 15:56:30 +0000

I'm using xml files to store documents annotations.
All my documents are in global namespace.

So lets say I created the following configuration file:

.Blackboard_Page.dcm.xml

<?xml version="1.0" encoding="utf-8"?>
<doctrine-mongo-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mongo-mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mongo-mapping.xsd">
<document name="\Blackboard_Page" collection="blackboard.pages">
<field fieldName="_id" name="_id" id="true"/>
...
</document>
</doctrine-mongo-mapping>

When I try to get the document using the following code:

foreach($dm->createQueryBuilder("\Blackboard_Page")...~~>getQuery()~~>execute() as $page) {}

it fails with Exception "Doctrine\ODM\MongoDB\MongoDBException: No identifier/primary key specified for Document 'Blackboard_Page'. Every Document must have an identifier/primary key."

The reason of the problem is behavior of the function "get_class".
See mongodb_odm\lib\Doctrine\ODM\MongoDB\Hydrator.php line 122:
$metadata = $this->dm->getClassMetadata(get_class($document));
for details.

When the code pass an instance of the document which belongs to global namespace the function "get_class()" returns class name without "\" prefix
and AbstractFileDriver->findMappingFile convert such class name into file name without leading dot (".") (something like "Blackboard_Page.dcm.xml" instead of ".Blackboard_Page.dcm.xml").
And it causes the exception.

Patching of the method "AbstractFileDriver->findMappingFile" does not help.
The problem is more complicated than it looks like because get_class() is used in a lot of places in the code.

[MODM-101] Following documentation still does not produce a working bootstrap.

Sat, 19 Feb 2011 18:25:12 +0000

Setting up following the documentation found at http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/reference/introduction/en#introduction produces the following errors.

PHP Fatal error: Class 'Doctrine\MongoDB\Configuration' not found in C:\Inetpub\sites\phpdev\public\mongodb_odm\lib\Doctrine\ODM\MongoDB\Configuration.php on line 43
PHP Stack trace:
PHP 1.

{main}

() C:\Inetpub\sites\phpdev\public\index.php:0
PHP 2. Doctrine\Common\ClassLoader->loadClass() C:\Inetpub\sites\phpdev\public\mongodb_odm\lib\vendor\doctrine-common\lib\Doctrine\Common\ClassLoader.php:0
PHP 3. require() C:\Inetpub\sites\phpdev\public\mongodb_odm\lib\vendor\doctrine-common\lib\Doctrine\Common\ClassLoader.php:148

Is there something missing from the documentation?

[MODM-100] XmlDriver and "discriminatorMap" for "EmbedMany"

Mon, 20 Dec 2010 16:06:02 +0000

Please correct me if i'm wrong but it looks like that current implementation of XmlDriver does not support the following feature:

"discriminatorMap" for "EmbedMany"

http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/reference/embedded-mapping/en#mixing-document-types

<?php

class User
{
/**

@EmbedMany(
discriminatorMap= { * "download"="DownloadTask", * "build"="BuildTask" * }
)
*/
private $tasks = array();
}

This feature is very important for our project and without it looks like that we have to move to Docblock annotations instead of XML format which could be rather painful and time consuming.

[MODM-99] ODM tests drop all collections from all databases on the MongoDB server

Mon, 20 Dec 2010 16:40:33 +0000

Recently I run ODM tests in my sandbox and found out that all collections in all databases were dropped after that.
Thanks god I did run it in my sandbox only which has own database instance.

After reviewing the code I found out that Doctrine\ODM\MongoDB\Tests\BaseTest->tearDown() method cleans up the whole MongoDB server after running the tests.

From one hand such extremely unsafe behavior is not mentioned anywhere from another hand there are no ways to work around it currently but only changing the tests code.

It would be really great if there is a way to specify MongoDB connection parameters for ODM tests or at least change tests code in order to drop only databases which were created during the test
and no others else.

Thank you.

[MODM-98] Partial UnitOfWork clear on runtime defaultDb change

Mon, 20 Dec 2010 16:50:15 +0000

Actually I am not sure if this is a bug or just ODM limitation, but there is a use-case for MongoDb which doesn't fit well with current ODM implementation.

Imagine SaaS service, where each client has his own DB. Documents and collections are all the same, except most of them are stored in different DBs, depending on context.

It works pretty well with ODM defaultDB configration setting, until you need to process data from different dbs (e.g. iterate db by db in CLI script). When you try to change default db, repositories and persisters stay there and all keep a reference to initial DB. And they don't get reset on UnitOfWork->clear(). It would be great to have runtime defaultDb switching out of the box, but if that is a problem, maybe you can advice on how this could be handled?

[MODM-97] FindAndModify does not return an object

Mon, 20 Dec 2010 16:50:34 +0000

Boolean true is returned instead of an object after a FindAndModify command is successfully executed.

$c = $dm->createQuery('downloads')
->findAndModify(array('new' => true))
~~>field('key')~~>equals('file1')
->update()
~~>field('counter')~~>inc(1)
->execute();

echo gettype($c); // boolean

[MODM-96] YamlDriver Symfony Components Namespace Issue

Mon, 20 Dec 2010 16:51:29 +0000

In the YamlDriver.php the namespace is incorrect I pressume. It should be \Symfony\Components\Yaml\Yaml. Its missing a 's' in Component

Current in Master :
protected function loadMappingFile($file)
{
return \Symfony\Component\Yaml\Yaml::load($file);
}

Desired Outcome
protected function loadMappingFile($file)
{
return \Symfony\Components\Yaml\Yaml::load($file);
}

[MODM-95] Persisting a document that had embedded documents prior to being removed results in a document with no embedded documents

Wed, 24 Nov 2010 13:02:52 +0000

1) Persist a document with embedded documents
2) Load document into memory (store in variable)
3) Remove document using ODM
4) Persist loaded document back to DB using ODM
5) Embedded documents are now gone

I have created a new failing test in the ODM and requested a pull

[MODM-94] $or operator

Mon, 15 Nov 2010 12:11:57 +0000

Hello,

MongoDB proposes an operator $or

http://www.mongodb.org/display/DOCS/Advanced+Queries#AdvancedQueries-%24or

Can you add this feature in Doctrine\ODM\MongoDB\Query

Thank you

Julien

[MODM-93] YAML and XML mapping drivers ignore discriminatorField and discriminatorMap

Wed, 24 Nov 2010 13:13:32 +0000

The discriminatorField and discriminatorMap options are ignored by both the YAML and XML drivers.

Example:
This mapping fails to store the discriminator in the type field and instead uses _doctrine_class_name as the discriminatorField the mapping also reverts to using class names.

 
<?xml version="1.0" encoding="UTF-8"?>
<doctrine-mongo-mapping>
    <document name="Application\Test\Document\Group" collection="groups">
        <field name="id" fieldName="id" id="true" />
        <field name="name" fieldName="name" type="string" />
        <embed-many field="people" discriminator-field="type">
            <discriminator-map>
                <discriminator-mapping class="Admin" value="Admin" />
                <discriminator-mapping class="User" value="User" />
            </discriminator-map>
        </embed-many>
    </document>
</doctrine-mongo-mapping>

I think that this is also a problem for referenced documents as well, as the code for the two is nearly identical.

I refactored addEmbedMapping and addReferenceMapping to call the same function addDocumentMapping
Commit can be found here http://github.com/dordille/mongodb-odm/commit/41ce2ee126ff7f82610130704dbec451384bfdd3

[MODM-92] Changing all data in embedMany collections can create duplicate embedded objects

Tue, 23 Nov 2010 16:20:55 +0000

Repeatable in the following use case, when the default pushPull strategy is used for an embedMany collection:

Persist an object with a single embedded object in its embedMany collection. Flush/clear/refetch.
Clear the collection and add a new embedded object. Flush/clear/refetch.
The containing object's collection now has two copies of the replacement object from the previous step.

I investigated this as best I could, and traced the problem to BasicDocumentPersister::prepareUpdateData() and the data it receives from UnitOfWork's changeset.

The UoW changeset simply reports the old/new embedded collections as arrays of raw data. This makes BasicDocumentPersister unable to distinguish whether a $set or $pullAll/$pushAll is an appropriate course of action, since it cannot discern whether the embedded objects are actually different (by SPL object hash) or merely changed. Following the logic in prepareUpdateData(), we end up doing two things when processing the update for the collection field:

Since old !== new, and we're a collection field type, generate pull/push commands based on the delete/insert diffs.
Since we're embedded and new evalutes to true, recursively call prepareUpdateData() on ourself, which will then go on to generate set commands.

This chain of commands will then reach BasicDocumentPersister::update() later on and given the logic check within:

> if ((isset($update[$this->cmd . 'pushAll']) || isset($update[$this->cmd . 'pullAll'])) && isset($update[$this->cmd . 'set'])) ...

The $set command will be executed first, followed by $pullAll/$pushAll later. This $set actually changes the very data that $pullAll expects to remove, so $pullAll will do nothing but $pushAll will still insert a copy of our new data. The end result is that we now have two copies of our new data in the collection.

[MODM-91] Document unnecessarily persisted when embedded documents have null properties

Wed, 24 Nov 2010 13:14:48 +0000

The setup is a document that has an embedded document. If the embedded document is persisted with at least one field set to null, the changeset for the parent document will include the embedded document, even if no changes have been made.

The reason is that the "$orgValue" in UnitOfWork::computeChangeSet() won't contain the null field at all, while the "$actualValue" contains the field properly set to a null value.

Test coverage and fix to follow.

[MODM-90] UnitOfWork incorrectly flushes certain documents with embedded documents on first flush

Wed, 20 Oct 2010 12:52:06 +0000

With documents that have embedded documents, the changeset is sometimes calculated incorrectly so that unmodified documents are flushed unnecessarily. This is similar in spirit to #~~MODM-83~~, but this isn't covered by that fix.

This can be seen when the document has an embedded document that uses a discriminator map. When calculating the changeset, the original value will have the discriminator field and value present while the actual value does not contain the discriminator field.

Covering tests with fixes to follow shortly.

[MODM-89] CLONE -UnitOfWork incorrectly updates all documents with embedded documents on flush

Wed, 24 Nov 2010 14:52:29 +0000

I use the MODM-83 fix, now i cant delete childrens with a other embedded document:

The complete document

{
   "_id" : ObjectId("4caeea835634c915360a0000"),
   "categories" : {
     "0" : {
       "id" : ObjectId("4cbd55f55634c99177030000"),
       "name" : "neue Kategorie",
       "questions" : {
         "0" : {
           "id" : ObjectId("4cbd55f75634c99177040000"),
           "name" : "neue Frage",
           "relevance" : 0,
           "multi" : 0,
           "answertype" : 0,
           "other" : 0
        }
      }
    }
  },
   "description" : "pipapo!",
   "name" : "ich bin ein Katalog",
   "version" : 1
}

Now i add a new answer too the question:

The question with the new answer

"questions" : {
         "0" : {
           "answers" : {
             "0" : {
               "id" : ObjectId("4cbd56b95634c99b5b090000"),
               "name" : "neue Antwort"
            }
          },
           "answertype" : 0,
           "id" : ObjectId("4cbd55f75634c99177040000"),
           "multi" : 0,
           "name" : "neue Frage",
           "other" : 0,
           "relevance" : 0
        } 
}

When i delete now the new answer i have a empty array and i cant delete the question from the categorie.

The unkillable question

"questions" : {
         "0" : {
           "answers" : [
            
          ],
           "answertype" : 0,
           "id" : ObjectId("4cbd55f75634c99177040000"),
           "multi" : 0,
           "name" : "neue Frage",
           "other" : 0,
           "relevance" : 0
        }
      }

Its a unkillable entry now.
Sorry for my bad english.

[MODM-88] Selecting a subset of properties and then flushing causes database corruption

Wed, 24 Nov 2010 14:10:10 +0000

Pretty simple to reproduce. Here is the code from our own application. All we wanted to do was to select a subset of fields from the Article document, and found that if we did that and then did anything to cause the DM to mark those documents as modified, when they get flushed to mongo it corrupts your data. For example, article has a property "published" which is set to 1, and after I run this code below, it will set the "published" property to "null" on all documents.

$class = 'Bundle\ArticleBundle\Document\Article';
$documents = $dm->createQuery($class)~~>select('_id','title','user')~~>execute();
foreach($documents as $document)

{ $document->getTitle(); }

$dm->flush();
exit;

[MODM-87] get_class() expects parameter 1 to be object, array given

Wed, 24 Nov 2010 14:10:31 +0000

The commit on October 4th introduced a bug for me.
Exactly this line:

http://github.com/doctrine/mongodb-odm/commit/8bd3aef4055cfded62687d5ad0e762e3f12a473d#commitcomment-167197

Now I always get an error, because embeddedDocument is an array, and so get_class fails.

[MODM-86] Order of keys in embedded document need to be enforced

Wed, 24 Nov 2010 14:10:48 +0000

Order of keys in embedded bson hashes in mongodb matters, so you can't $pullAll an embedded document if the order of keys is different from the one in mongodb:

code
{
_id: ObjectId('123'),
addresses: [

{ street: 'SomeStreet', zipCode: '11111' }

{ zipCode: '22222', street: 'AnotherStreet' }

,
]
}
/code

then query like:

code
db.collection.update({_id: ObjectId('123')}, {$pullAll: {addresses: [

{ zipCode: '11111', street: 'SomeStreet' }

]}})
/code

would fail, because the order of keys ('zipCode', 'street') is different from the one stored in mongo ('street', 'zipCode'). More can be found here http://jira.mongodb.org/browse/SERVER-1914

Therefore, we need to force the order on every insert and update for consistency.

[MODM-85] Saving a array over the top of a PersistentCollection results in duplicated data

Wed, 24 Nov 2010 14:11:03 +0000

If you take an document that has a referenceMany and overwrite a PersistentCollection of data with an array, even of the same data, the data is appended to the collection instead of replacing it.

[MODM-84] prePersist and postPersist called twice

Wed, 24 Nov 2010 14:11:23 +0000

It appears that the prePersist and postPersist lifecycle events are called twice when persisting and removing a document. Not sure yet if this happens because its an inherited class, will setup a test to try and show behavior.

[MODM-83] UnitOfWork incorrectly updates all documents with embedded documents on flush

Tue, 19 Oct 2010 07:01:29 +0000

UnitOfWork incorrectly contains every managed document with embedded documents. All embedded documents are marked as updated. The whole mess will be updated on the next flush, regardless of whether said documents have actually changed.

Branch here: http://github.com/opensky/mongodb-odm/tree/MODM-83

Test case here: http://github.com/opensky/mongodb-odm/commit/af4373b58dd5da0bea5a0f8c4da30dde5ed1f266

Here's what the document changeset looks like in preUpdate and postUpdate:

preUpdate "Doctrine\ODM\MongoDB\Tests\Functional\Ticket\MODM83OtherDocument"

array(1) {
  ["name"]=>
  array(2) {
    [0]=>
    string(8) "Neighbor"
    [1]=>
    string(3) "Bob"
  }
}

postUpdate "Doctrine\ODM\MongoDB\Tests\Functional\Ticket\MODM83OtherDocument"

array(1) {
  ["name"]=>
  array(2) {
    [0]=>
    string(8) "Neighbor"
    [1]=>
    string(3) "Bob"
  }
}

preUpdate "Doctrine\ODM\MongoDB\Tests\Functional\Ticket\MODM83TestDocument"

array(1) {
  ["embedded"]=>
  array(2) {
    [0]=>
    array(1) {
      ["name"]=>
      string(5) "Child"
    }
    [1]=>
    array(2) {
      ["name"]=>
      string(5) "Child"
      ["originalObject"]=>
      object(Doctrine\ODM\MongoDB\Tests\Functional\Ticket\MODM83TestEmbeddedDocument)#86 (1) {
        ["name"]=>
        string(5) "Child"
      }
    }
  }
}

postUpdate "Doctrine\ODM\MongoDB\Tests\Functional\Ticket\MODM83TestDocument"

array(1) {
  ["embedded"]=>
  array(2) {
    [0]=>
    array(1) {
      ["name"]=>
      string(5) "Child"
    }
    [1]=>
    array(2) {
      ["name"]=>
      string(5) "Child"
      ["originalObject"]=>
      object(Doctrine\ODM\MongoDB\Tests\Functional\Ticket\MODM83TestEmbeddedDocument)#86 (1) {
        ["name"]=>
        string(5) "Child"
      }
    }
  }
}

[MODM-82] Add New Attribute "idGetter" to allow accessing the ID without triggering lazy-load

Fri, 4 Mar 2011 10:46:11 +0000

access the ID of a proxy without loading it.

See DDC-687

[MODM-81] No reference to a loaded document if proxy id = document id

Wed, 24 Nov 2010 14:12:10 +0000

If I load a document and it has an internal reference to the same document with the same ID, only responds to changes in the proxy document. The main document will not be considered and any change has no effect.

[MODM-80] Changeset for embedded documents calculates to an unnecessary pullAll() and pushAll() in some cases.

Wed, 24 Nov 2010 14:12:27 +0000

When embedded documents are persisted and then some of them are removed in just the right way, the resulting update will issue a $pullAll for ALL of the embedded documents and then a $pushAll on whichever embedded documents weren't actually removed. Obviously, only a $pullAll on the removed items is necessary.

Additionally, while the $pullAll and the $pushAll seem like they should add up to the correct finish (though inefficient), the removed items appear to not be removed correctly. The $pullAll falls correctly into the if loop found here: http://github.com/doctrine/mongodb-odm/blob/master/lib/Doctrine/ODM/MongoDB/Persisters/BasicDocumentPersister.php#L230, but the end result of that $pullAll in this case is that some items are not removed.

A test case for this is here: http://github.com/weaverryan/mongodb-odm/commit/9968697a2c07e31ecfdd8d55ecbf9bf39183d01e. The first case, testModifyGroupsArrayDirectly() tests for this. The second case relates to ~~MODM-79~~.

Thanks - I've found the issue particular strange to nail down and inconsistent. If you spot any issues in my test cases, let me know.

[MODM-79] Referenced and Embedded document duplicates are inserted

Wed, 24 Nov 2010 14:13:02 +0000

I have a document with several collections referencing documents in other collections.

Doctrine ODM seems to have issues with ArrayCollections and realizing that elements are being taken out. I call ArrayCollection->clear() on those collections but when calculating the changeset Doctrine does not realize that some were deleted.

My scenario is following: I have a REST API. On the API I use Doctrine ODM as data backend.

Now when I get a request to update an object, I get the passed ID of the object, and populate all the fields.

However with collections I call clear() on the collection and then re-add all passed elements. This might not be a very elegant solution, but I don't have to worry about added / changed / deleted items. I pretty much just set a new collection.

However, when persisting this document, Doctrine does not seem to notice that I cleared the collection. It just adds all the objects I added to the collection. Therefore I have a lot of duplicate items in my collection.

[MODM-78] mappedSuperclass as parent embedded class

Fri, 11 Feb 2011 15:58:41 +0000

Hi,

i have 3 documents : a contact, a professional address and a personal address
A contact embed the 2 addresses

The Contact class inherits from an abstract class DomainAbstract
The 2 addresses classes inherits from an abstract class Address which inherits from DomainAbstract

DomainAbstract <- Contact
DomainAbstract <- Address <- PersonalAddress, ProfessionalAddress

DomainAbstract is defined as mappedSuperclass

Address is defined as mappedSuperclass

PersonalAddress, ProfessionalAddress are embeddedDocument

But the fields defined by address are not inherited by embedded PersonalAddress and ProfessionalAddress ( but the fields in domainAbstract are like expected)

I think, 2 levels of inheritance and embedded document is wrong...

thx for help

ps: yaml mapping

[MODM-77] Add "addToSet" strategy for collections / embedMany / referenceMany

Wed, 24 Nov 2010 14:35:37 +0000

There are cases when collection must not contain duplicates. Mongo has "$addToSet" atomic command for such cases. It would be great to have a separate strategy for that command when persisting collections / embedMany / referenceMany.

As far as I understand, Doctrine already supports "set" and "pushPull" strategy, so adding "addToSet" strategy should be possible, right?

[MODM-76] I get an error when trying to persist a document

Mon, 20 Sep 2010 11:53:34 +0000

This is the error I get:

get_class() expects parameter 1 to be object, array given.

Stack Trace:

#0 [internal function]: {closure}(2, 'get_class() exp...', '/Library/WebSer...', 562, Array)
#1 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/Persisters/BasicDocumentPersister.php(562): get_class(Array)
#2 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/Persisters/BasicDocumentPersister.php(545): Doctrine\ODM\MongoDB\Persisters\BasicDocumentPersister->prepareReferencedDocValue(Array, Array)
#3 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/Persisters/BasicDocumentPersister.php(536): Doctrine\ODM\MongoDB\Persisters\BasicDocumentPersister->prepareValue(Array, Array)
#4 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/Persisters/BasicDocumentPersister.php(463): Doctrine\ODM\MongoDB\Persisters\BasicDocumentPersister->prepareValue(Array, Array)
#5 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/Persisters/BasicDocumentPersister.php(209): Doctrine\ODM\MongoDB\Persisters\BasicDocumentPersister->prepareUpdateData(Object(App_Model_Ticket))
#6 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/UnitOfWork.php(771): Doctrine\ODM\MongoDB\Persisters\BasicDocumentPersister->update(Object(App_Model_Ticket), Array)
#7 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/UnitOfWork.php(281): Doctrine\ODM\MongoDB\UnitOfWork->executeUpdates(Object(Doctrine\ODM\MongoDB\Mapping\ClassMetadata), Array)
#8 /Library/WebServer/Documents/ktapi/library/Doctrine/ODM/MongoDB/DocumentManager.php(503): Doctrine\ODM\MongoDB\UnitOfWork->commit(Array)
#9 /Library/WebServer/Documents/ktmodels/library/App/Model/Service/Dao/Doctrine.php(26): Doctrine\ODM\MongoDB\DocumentManager->flush()
#10 /Library/WebServer/Documents/ktmodels/library/App/Model/Service/Abstract.php(54): App_Model_Service_Dao_Doctrine->save(Object(App_Model_Ticket))
#11 /Library/WebServer/Documents/ktmodels/library/App/Model/Abstract.php(215): App_Model_Service_Abstract->save(Object(App_Model_Ticket))
#12 /Library/WebServer/Documents/ktmodels/library/App/Model/Ticket.php(84): App_Model_Abstract->save()
#13 /Library/WebServer/Documents/ktapi/application/controllers/TicketController.php(145): App_Model_Ticket->save()
#14 /Library/WebServer/Documents/ktapi/library/Zend/Controller/Action.php(513): TicketController->putAction()
#15 /Library/WebServer/Documents/ktapi/library/Zend/Controller/Dispatcher/Standard.php(295): Zend_Controller_Action->dispatch('putAction')
#16 /Library/WebServer/Documents/ktapi/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#17 /Library/WebServer/Documents/ktapi/library/Zend/Application/Bootstrap/Bootstrap.php(97): Zend_Controller_Front->dispatch()
#18 /Library/WebServer/Documents/ktapi/library/Zend/Application.php(366): Zend_Application_Bootstrap_Bootstrap->run()
#19 /Library/WebServer/Documents/ktapi/public/index.php(34): Zend_Application->run()
#20 {main}

Please tell me how I can be more precise or of more help. Do you need my models for debugging? (I do not want to post them here).

[MODM-75] mappedSuperclass and embedded document not working with yaml mapping

Wed, 24 Nov 2010 14:49:31 +0000

all documents inherits from an abstract class Cgd\DomainObject\DomainObjectAbstract

The document App\Entity\Contact\Contact has many App\Entity\Contact\Program

abstract class Cgd\DomainObject\DomainObjectAbstract

mappedSuperclass

#Cgd.DomainObject.DomainObjectAbstract.dcm.yml
Cgd\DomainObject\DomainObjectAbstract:
  type: mappedSuperclass
  fields:
    id:
      fieldName: id
      id: true
    createdAt:
      fieldName: createdAt
      type: date
    updatedAt:
      fieldName: updatedAt
      type: date
  lifecycleCallbacks:
    prePersist: [onPreInsert]
    preUpdate: [onPreUpdate]

Here the inherited class

class App\Entity\Contact\Contact extends Cgd\DomainObject\DomainObjectAbstract

InheritedClass

#App.Entity.Contact.Contact.dcm.yml
App\Entity\Contact\Contact:
  collection: contacts
  type: document
  fields:
    email:
      fieldName: email
      type: string
    status:
      fieldName: status
      type: int
  embedMany:
    programs:
      targetDocument: App\Entity\Contact\Program
      cascade: all

The embedded

class App\Entity\Contact\Program extends Cgd\DomainObject\DomainObjectAbstract

embeddedDocument

#App.Entity.Contact.Program.dcm.yml
App\Entity\Contact\Program:
  type: embeddedDocument
  fields:
    name:
      fieldName: name
      type: string

No field from abstract class are populated in embedded document

[MODM-74] lifecycleCallbacks are not inherited from mappedSuperclass in yaml mapping

Wed, 24 Nov 2010 14:36:10 +0000

The abstract class :

abstract class Cgd\DomainObject\DomainObjectAbstract

mappedSuperclass

#Cgd.DomainObject.DomainObjectAbstract.dcm.yml
Cgd\DomainObject\DomainObjectAbstract:
  type: mappedSuperclass
  fields:
    id:
      fieldName: id
      id: true
    createdAt:
      fieldName: createdAt
      type: date
    updatedAt:
      fieldName: updatedAt
      type: date
  lifecycleCallbacks:
    prePersist: [onPreInsert]
    preUpdate: [onPreUpdate]

Here the inherited class

class App\Entity\Contact\Contact extends Cgd\DomainObject\DomainObjectAbstract

InheritedClass

#App.Entity.Contact.Contact.dcm.yml
App\Entity\Contact\Contact:
  collection: contacts
  type: document
  fields:
    email:
      fieldName: email
      type: string
    status:
      fieldName: status
      type: int

If i add the lifecycleCallbacks in the InheritedClass yaml config. Events are working

[MODM-73] Neo4j (Graph oriented Database)

Wed, 24 Nov 2010 14:36:41 +0000

MongoDB Object Document Mapper is a particularly nice added value and represent a great interest for integrating into php framework.
MongoDB is one of the most representative actor in the document oriented databse and my suggestion here would be to implement
the same for the most representative graph oriented database which is Neo4J.

Someone tried an overall PHP approach and his choice seems an interesting compromise => http://wiki.neo4j.org/content/PHP.
A more elaborated approach around a doctrine work would be ore than helpful.

[MODM-72] New property 'options' in Annotations

Wed, 24 Nov 2010 14:45:32 +0000

It would be great for many purposes to add a property options to document annotations like this:

/** @Field(type="mytype", options={}) */

the options should also be implemented in the MetadataClass.

[MODM-71] "Getting Started" Canonical example is needlessly confusing

Fri, 3 Sep 2010 13:21:46 +0000

http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/reference/introduction/en#introduction

The '/path/to/doctrine/' placeholders are nondescript and confusing to new users, especially when the only way to make them work is to pass in just the path to the DocumentRoot. That should be mentioned, cleaned up, re-purposed, re-clarified, reverted, or whichever adjective of adjustment is suitable.

[MODM-70] Updates of documents after read

Duplicate — Wed, 24 Nov 2010 14:48:43 +0000

When I save a document and then read it again updated the document with the initial values.

The following log output when saving Doctrine:

Array
(
    [storing] => 1
    [file] => /app/tests/cases/models/asset/test.swf
    [document] => Array
        (
            [filename] => a3f06b4b882ee28ee8d8c7a5e6ab67e6.swf
            [php] => ass
        )

    [class] => Documents\Assets\Asset
    [db] => test
    [collection] => assets_files
)

Array
(
    [batchInsert] => 1
    [num] => 1
    [data] => Array
        (
            [00000000341a62a40000000001574585] => Array
                (
                    [cS] => 3
                    [rS] => 3
                    [co] => 0
                    [ca] => 0
                    [lvl] => 0
                    [nb] => 0
                    [sex] => 0
                    [na] => Building01
                    [typ] => building
                    [as] => Array
                        (
                            [$ref] => assets_files
                            [$id] => MongoId Object
                                (
                                )

                            [$db] => test
                        )

                )

        )

    [class] => Documents\Assets\MapAsset
    [db] => test
    [collection] => map_assets
)

Then read:

Array
(
    [findOne] => 1
    [query] => Array
        (
            [_id] => MongoId Object
                (
                )

        )

    [fields] => Array
        (
        )

    [class] => Documents\Assets\MapAsset
    [db] => test
    [collection] => map_assets
)

Then check for updates Document:

$this->dm->getUnitOfWork()->computeChangeSets();
$update = $this->dm->getUnitOfWork()->getDocumentPersister('Documents\Assets\MapAsset')->prepareUpdateData($mapAsset);
print_r($update);

Array
(
    [$set] => Array
        (
            [cS] => 3
            [rS] => 3
            [co] => 0
            [ca] => 0
            [lvl] => 0
            [nb] => 0
            [sex] => 0
            [na] => Building01
            [typ] => building
            [as] => Array
                (
                    [$ref] => assets_files
                    [$id] => MongoId Object
                        (
                        )

                    [$db] => test
                )

        )

)

Why is there an update even though it set the initial values? In Mongo are the values set correctly!

Then I run a flush:

Array
(
    [update] => 1
    [criteria] => Array
        (
            [_id] => MongoId Object
                (
                )

        )

    [newObj] => Array
        (
            [$set] => Array
                (
                    [uploadDate] => 0.63800000 1283421657
                    [length] => 4222
                    [chunkSize] => 262144
                    [md5] => 2af70cb102026bde0cf9f181780b642c
                )

        )

    [options] => Array
        (
        )

    [class] => Documents\Assets\Asset
    [db] => test
    [collection] => assets_files
)

Array
(
    [update] => 1
    [criteria] => Array
        (
            [_id] => MongoId Object
                (
                )

        )

    [newObj] => Array
        (
            [$set] => Array
                (
                    [cS] => 3
                    [rS] => 3
                    [co] => 0
                    [ca] => 0
                    [lvl] => 0
                    [nb] => 0
                    [sex] => 0
                    [na] => Building01
                    [typ] => building
                    [as] => Array
                        (
                            [$ref] => assets_files
                            [$id] => MongoId Object
                                (
                                )

                            [$db] => test
                        )

                )

        )

    [options] => Array
        (
        )

    [class] => Documents\Assets\MapAsset
    [db] => test
    [collection] => map_assets
)

1st Doctrine update GridFS file and destroyed it! Wrong value for uploadDate and the file can then be displayed in the browser no longer!

2nd Why did he updatet The Document with the same values that are already there in Mongo and the initial values are?

Here is my test code:

$asset = APP_TEST_CASES . DS . 'models' . DS . 'asset' . DS . 'test.swf';
$assetInfo = pathinfo($asset);
$assetName =  md5($assetInfo['basename'] . time() . mt_rand()) . '.' . $assetInfo['extension'];
$assetFile = new Documents\Assets\Asset($asset, $assetName);

$cSpan = 3;
$rSpan = 3;
$mapAsset = new Documents\Assets\MapAsset('Building01', 'building', $cSpan, $rSpan, null, $assetFile);
$this->assertEqual($mapAsset->getColumnSpan(), $cSpan);
$this->assertEqual($mapAsset->getRowSpan(), $rSpan);
$this->assertEqual($mapAsset->getSpans(), array('columnSpan' => $cSpan, 'rowSpan' => $rSpan));

$this->dm->persist($mapAsset);
$this->dm->flush();
$this->dm->refresh($mapAsset);

$this->dm->getUnitOfWork()->computeChangeSets();
$update = $this->dm->getUnitOfWork()->getDocumentPersister('Documents\Assets\MapAsset')->prepareUpdateData($mapAsset);
debug($update);
$this->dm->flush();

Here is my test Documents:

namespace Documents\Assets;

/**
 * @Document(collection="assets_files")
 */
class Asset {
	/**
	 * @Id
	 * @var string
	 */
	protected $_id;
	/**
	 * @File
	 */
	protected $_file;
	/**
	 * @String(name="filename")
	 */
	protected $_filename;
	/**
	 * @Field(name="uploadDate")
	 * @var int
	 */
	protected $_uploadDate;
	/**
	 * @Field(name="length")
	 * @var int
	 */
	protected $_length;
	/**
	 * @Field(name="chunkSize")
	 * @var int
	 */
	protected $_chunkSize;
	/**
	 * @Field(name="md5")
	 * @var string
	 */
	protected $_md5;
	/**
	 * @Field(name="contentType")
	 * @var string
	 */
	protected $_contentType;
	/**
	 * @Field(name="metadata")
	 * @var string
	 */
	protected $_metadata;

	public function __construct($file, $filename = null) {
		$this->_file = $file;
		$this->_filename = $filename;
	}
	
	// ..
}

namespace Documents\Assets;

/**
 * @Document(collection="map_assets")
 */
class MapAsset {
	/**
	 * @Id
	 * @var string
	 */
	protected $_id;

	/**
	 * @ReferenceOne(
	 *	targetDocument="Documents\Assets\Asset",
	 *	name="as",
	 *	cascade={"persist", "remove"}
	 *	)
	 * @var Documents\Assets\Asset
	 */
	protected $_asset;

	// ..
}

[MODM-69] implement commands to generate documents

Sat, 12 Feb 2011 11:56:10 +0000

implement commands to generate documents

[MODM-68] port EntityGenerator to DocumentGenerator

Sat, 12 Feb 2011 11:56:26 +0000

port EntityGenerator to DocumentGenerator

[MODM-67] EmbeddedDocument - no LifecycleCallbacks

Tue, 31 Aug 2010 12:15:17 +0000

LifecycleCallbacks in EmbeddedDocument are not called

/**
 * @EmbeddedDocument
 * @HasLifecycleCallbacks
 */
class SocialNetworkUser {

	/**
	 * @Int(name="id")
	 * @var int
	 */
	protected $id;
	/**
	 * @String(name="fN")
	 * @var string
	 */
	protected $firstName;
	/**
	 * @String(name="lN")
	 * @var string
	 */
	protected $lastName;
	/**
	 * @NotSaved
	 * @var string
	 */
	protected $name;

        // ....

	/**
	 * @PostLoad
	 */
        public function postLoad() {
		$this->name = $this->firstName . ' ' . $this->lastName;
	}
}

/**
 * @Document(collection="users")
 */
class User {
	/**
	 * @Id
	 */
	protected $id;
	/**
	 * @EmbedOne(
	 * 	discriminatorField="php",
	 * 	discriminatorMap={
	 * 		"fbu"="Documents\SocialNetworkUser "
	 * 	},
	 * 	name="snu",
	 * 	cascade={"persist", "remove"}
	 * )
	 */
	protected $socialNetworkUser;
}

$_user = $this->dm->findOne('Documents\User', array('snu.id' => $uid));
print_r($_user->getSocialNetworkUser()->getName())

$name is empty.
postLoad is never called after load

[MODM-66] Bug when persisting referenced collection

Duplicate — Mon, 6 Sep 2010 14:37:32 +0000

After adding new entry to referenced collection of existing document, ODM generates invalid update query.

Here is a test case:

/** @Document(db="tests", collection="tests") */
class a
{
    /** @Id */
    protected $id;

    /** @ReferenceMany(targetDocument="b", cascade="all") */
    protected $b;

    function __construct($b) {$this->b = new ArrayCollection($b);}

    function getB() {return $this->b;}
}

/** @Document(db="tests", collection="tests2") */
class b
{
    /** @Id */
    protected $id;

    /** @String */
    protected $tmp;

    function __construct($v) {$this->tmp = $v;}
}

$a = new a(array(new b('first')));
$dm->persist($a);
$dm->flush(); // flush causes notices
$dm->refresh($a);

$a->getB()->add(new b('second'));
$dm->persist($a);
$dm->flush();
$dm->refresh($a);

print_r($a->getB()->toArray());

Expecting following output:

Array
(
    [0] => b Object
        (
            [id:protected] => 4c7c9eea0f9d502005000000
            [tmp:protected] => first
        )

    [1] => b Object
        (
            [id:protected] => 4c7c9eea0f9d502005020000
            [tmp:protected] => second
        )

)

But getting:

Array
(
    [0] => b Object
        (
            [id:protected] => 4c7c9eea0f9d502005000000
            [tmp:protected] => first
        )

    [1] => b Object
        (
            [id:protected] => 4c7c9eea0f9d502005000000
            [tmp:protected] => first
        )

    [2] => b Object
        (
            [id:protected] => 4c7c9eea0f9d502005020000
            [tmp:protected] => second
        )

)

[MODM-65] EmbeddedDocument - Incorrect assignment of special field names on save

Mon, 30 Aug 2010 14:40:05 +0000

If I have a document which has a EmbeddedDocument and this other name used as the variable name. Thus, when saving but not used by the special reserved name of the variable name. But when read out of the special reserved name is used. so is my EmbeddedDocument always empty when the specific name are different. Furthermore, when I set no specific name for it is also EmbeddedDocument empty.

Example:

/**
 * @EmbeddedDocument
 */
class SocialNetworkUser {
	/**
	 * @Int(name="id")
	 * @var int
	 */
	protected $id;
	/**
	 * @String(name="fN")
	 * @var string
	 */
	protected $firstName;
	/**
	 * @String(name="lN")
	 * @var string
	 */
	protected $lastName;
}

/**
 * @Document(collection="users")
 */
class User {
	/**
	 * @Id
	 */
	protected $id;
	/**
	 * @EmbedOne(
	 * 	discriminatorField="php",
	 * 	discriminatorMap={
	 * 		"fbu"="Documents\SocialNetworkUser "
	 * 	},
	 * 	name="snu",
	 * 	cascade={"persist", "remove"}
	 * )
	 */
	protected $socialNetworkUser;
}

$user = $this->dm->findOne('Documents\User', array('snu.id' => $this->Facebook->getUser()));

print_r($user->getSocialNetworkUser()):

Documents\SocialNetworkUser  Object
(
    [id:protected] => // Commented
    [firstName:protected] => 
    [lastName:protected] => 
)

in Mongo:

Array
(
    [_id] => 4c7b4fc3ed1590814d050000
    [snu] => Array
        (
            [id] => // Commented
            [firstName] => Thomas
            [lastName] => Adam
            [php] => fbu
        )
)

Correct but should be:

Array
(
    [_id] => 4c7b4fc3ed1590814d050000
    [snu] => Array
        (
            [id] => // Commented
            [fN] => Thomas
            [lN] => Adam
            [php] => fbu
        )
)

[MODM-64] @DynamicFields

Mon, 30 Aug 2010 14:40:26 +0000

I suggest adding a new feature called @DynamicFields. The idea is from roman and documeneted here: http://github.com/romanb/couchdb-persistence-api/blob/master/src/main/java/org/code_factory/couch/annotations/DynamicFields.java

Idea: Save all "left-over" fields of the result in an array.

This would greatly enhance the flexibility of document mappers

[MODM-63] More errors when persisting gridfs files

Wed, 24 Nov 2010 14:37:24 +0000

Getting following errors when trying to persist GridFS file.

Trying to get property of non-object in file Doctrine\ODM\MongoDB\MongoCollection.php on line 196 
Undefined index: _id in file Doctrine\ODM\MongoDB\Persisters\BasicDocumentPersister.php on line 163

Unfortunately couldn't create reproducable test-case yet, but if that is not an obvious issue, please let me know, I'll try to dig deeper and get the test case.

[MODM-62] PHP warning when array is replaced with ArrayCollection: array_udiff_assoc(): Argument #2 is not an array

Mon, 30 Aug 2010 15:10:44 +0000

Simple test case to reproduce:

/** @Document(db="tests", collection="tests") */
class a {
    /** @Id */
    protected $id;

    /** @Collection */
    protected $b = array('test');

    function setB($b) {$this->b = $b;}
}

$a = new a();
$dm->persist($a);
$dm->flush();
$dm->refresh($a);

$a->setB(new ArrayCollection(array('test')));
$dm->persist($a);
$dm->flush();

Getting PHP warning:

PHP Warning:  array_udiff_assoc(): Argument #2 is not an array in Doctrine\ODM\MongoDB\Persisters\BasicDocumentPersister.php on line 458

[MODM-61] GridFs file is stored incorrectly after two flushes

Mon, 30 Aug 2010 15:30:05 +0000

GridFs file is stored incorrectly after two flushes.

Consider an example:

/** @Document(db="tests", collection="fs") */
class File
{
    /** @Id */
    protected $id;

    /** @File */
    protected $file;

    function  __construct($source) {$this->file = $source;}
}

$file = new File(__DIR__ . '/test.txt');

$dm->persist($file);
$dm->flush();
$dm->flush();

After second flush, doctrine will also store "file" property as if it was a regular object. Expecting:

{
  "_id": "4c777fc00f9d505407020000",
  "filename": "/test.txt",
  "uploadDate": {
    "sec": 1282899904,
    "usec": 0
  },
  "length": 10,
  "chunkSize": 262144,
  "md5": "76ce9f441de2ed5de337d391ad4516b7"
}

Actual result:

{
  "_id": "4c777f780f9d508416020000",
  "chunkSize": 262144,
  "file": {
    "file": {
      "_id": {},
      "filename": "/test.txt",
      "uploadDate": {
        "sec": 1282899832,
        "usec": 0
      },
      "length": 10,
      "chunkSize": 262144,
      "md5": "76ce9f441de2ed5de337d391ad4516b7"
    },
    "": {
      "w": 1,
      "wtimeout": 10000,
      "chunks": {
        "w": 1,
        "wtimeout": 10000
      },
      "": "fs.chunks"
    }
  },
  "filename": "/test.txt",
  "length": 10,
  "md5": "76ce9f441de2ed5de337d391ad4516b7",
  "uploadDate": {
    "sec": 1282899832,
    "usec": 0
  }
}

P.S. Unfortunately cannot use PHPUnit 3.5 right now to provide unit test.

[MODM-60] Need a way to find all documents from collection by their base class

Tue, 31 Aug 2010 05:17:55 +0000

Imagine a use case:

I have a set of classes, which extend abstract class BaseGridFsFile. All children classess are stored in same GridFs collection (using single collection inheritance).

But I cannot fetch all files from this collection, regardless their type. I know that I can use array of subclasses to fetch, but this won't work in my case, because there is no static DiscriminatorMap.

It whould be great if I could use something like this:

$files = $dm->find('BaseGridFsFile', $query);

and Doctrine would instantiate proper classes for found documents.

Is it possible?

[MODM-59] Exception: "The given document has no identity." when findOne query returns none from a MongoGridFs

Thu, 26 Aug 2010 10:53:10 +0000

When running a query against a GridFS that should return no results, I expect the return value to be null (as with normal documents) instead an InvalidArgumentException is thrown, with the message "The given document has no identity".

It appears the empty result is trying to be registered as a managed document with the UOW, because MongoCollection does not return null in this case.

[MODM-58] Update Collection API

Fri, 27 Aug 2010 11:48:24 +0000

need to update to reflect this change http://www.doctrine-project.org/jira/browse/DCOM-17

[MODM-57] The SchemaManager::createDocumentDB/createDatabases

Tue, 24 Aug 2010 10:31:43 +0000

Make ShemaManager execute an arbitrary command on selected db, to trigger actual db creation in SchemaManager::createDocumentDB/createDatabases.

[MODM-56] @PreUpdate & EmbedMany

Tue, 24 Aug 2010 11:38:03 +0000

Unable to find source-code formatter for language: php. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

// Article
namespace Bundle\ArticleBundle\Document;

use Bundle\CommentBundle\Document\Comment;
use Bundle\ExerciseCommonBundle\Document\Repository;

/**
 * @Document(
 *   collection="article",
 *   indexes={
 *     @Index(keys={"createdAt"="asc"})
 *   },
 *   repositoryClass="Bundle\ArticleBundle\Document\ArticleRepository"
 * )
 * @HasLifecycleCallbacks
 */
class Article
{
    /**
     * @Id
     */
    protected $id;
    /**
     * @ReferenceOne(targetDocument="Bundle\AccountBundle\Document\User")
     */
    protected $user;
    /**
     * @ReferenceOne(targetDocument="Bundle\ArticleBundle\Document\ArticleCategory")
     * @Validation({
     *      @NotBlank (message="Please select a category.")
     * })
     */
    protected $category;
    /**
     * @Field(type="string")
     */
    protected $slug;
    /**
     * @Field(type="string")
     * @Validation({
     *      @NotBlank (message="You forgot a Title?"),
     *      @MinLength(limit=4, message="Just a little too short.")
     * })
     */
    protected $title;
    /**
     * @Field(type="string")
     * @Validation({
     *      @NotBlank (message="Please summarize your article."),
     *      @MinLength(limit=100, message="Not long enough!"),
     *      @MaxLength(limit=200, message="A wee bit too long.")
     * })
     */
    protected $summary;
    /**
     * @Field(type="string")
     * @Validation({
     *      @NotBlank (message="Where's the beef?")
     * })
     */
    protected $body;
    
	/** 
	 * @EmbedMany(targetDocument="Bundle\CommentBundle\Document\Comment") 
	 * */
	protected $comments = array();
	
    /**
     * @Field(type="boolean")
     */
    protected $published = false;
    /**
     * @Field(type="date", nullable=false)
     */
    protected $createdAt;
    /**
     * @Field(type="date", nullable=false)
     */
    protected $updatedAt;

    public function getId()
    {
        return $this->id;
    }

    public function isNew() {
        return empty($this->id);
    }

    public function getUser()
    {
        return $this->user;
    }

    public function getCategory()
    {
        return $this->category;
    }

    public function getSlug()
    {
        return $this->slug;
    }

    public function setSlug($slug)
    {
        $this->slug = $slug;
    }

    public function setUniqueSlug()
    {
        $this->slug = Repository::Slugify($this->title);
    }

    public function isPublished()
    {
        if($this->published) {
            return true;
        }
        return false;
    }

    public function publish()
    {
        $this->published = true;
    }

    public function unpublish()
    {
        $this->published = false;
    }

    public function getSummary()
    {
        return $this->summary;
    }

    public function setSummary($summary)
    {
        $this->summary = $summary;
    }

    public function getTitle()
    {
        return $this->title;
    }

    public function setTitle($title)
    {
        $this->title = $title;
    }

    public function getBody()
    {
        return $this->body;
    }



    public function setBody($body)
    {
        $this->body = $body;
    }

    public function setUser($user) {
        $this->user = $user;
    }

    public function setCategory($category) {
        $this->category = $category;
    }

    public function getCreatedAt()
    {
        return $this->createdAt;
    }

    /**
     * It can be useful when writing fixtures
     * @param \DateTime $date
     * @return void
     */
    public function setCreatedAt(\DateTime $date)
    {
        $this->createdAt = $date;
    }

    public function getUpdatedAt()
    {
        return $this->updatedAt;
    }

    public function __toString()
    {
        return $this->title();
    }
    
    
	/**
	 * @return the $comments
	 */
	public function getComments() {
		return $this->comments;
	}    
    
	/**
	 * @param $comments the $comments to set
	 */
	public function setComments($comments) {
		$this->comments = $comments;
	}
    /** @PrePersist */
    public function incrementCreatedAt()
    {
        if(null === $this->createdAt) {
            $this->createdAt = new \DateTime();
        }
        $this->updatedAt = new \DateTime();
    }

    /** @PreUpdate */
    public function incrementUpdatedAt() {
        $this->updatedAt = new \DateTime();
    }

    public function fromArray(array $array)
    {
        foreach($array as $property => $value) {
            $this->$property = $value;
        }
    }
}

Unable to find source-code formatter for language: php. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

// Comment
<?php

namespace Bundle\CommentBundle\Document;

/**
 * @EmbeddedDocument
 */
class Comment
{
	
	/**
     * @Id
     */
    protected $id;
	
    /**
     * @Field(type="date", nullable=true)
     */
    protected $createdAt;

    /**
     * @Field(type="string", nullable=true)
     */
    protected $message;

    /**
     * @ReferenceOne(targetDocument="Bundle\AccountBundle\Document\User")
     */
    protected $user;

    /**
     * @return the $createdAt
     */
    public function getCreatedAt() {
        return $this->createdAt;
    }

    /**
     * @return the $message
     */
    public function getMessage() {
        return $this->message;
    }

    /**
     * @return the $user
     */
    public function getUser() {
        return $this->user;
    }

    /**
     * @param $createdAt the $createdAt to set
     */
    public function setCreatedAt($createdAt) {
        $this->createdAt = $createdAt;
    }

//    /** @PrePersist */
//    public function incrementCreatedAt()
//    {
//        if(null === $this->createdAt) {
//            $this->createdAt = new \DateTime();
//        }
//        $this->updatedAt = new \DateTime();
//    }
//
//    /** @PreUpdate */
//    public function incrementUpdatedAt() {
//        $this->updatedAt = new \DateTime();
//    }

    /**
     * @param $message the $message to set
     */
    public function setMessage($message) {
        $this->message = $message;
    }

    /**
     * @param $by_user_id the $by_user_id to set
     */
    public function setUser($user) {
        $this->user = $user;
    }
}

Unable to find source-code formatter for language: php. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

                $article = $this->odm->getRepository('Bundle\ArticleBundle\Document\Article')->find("someID");

		$newComment = new Comment();
		$newComment->setUser($user);
		$newComment->setMessage("PPPPOOOOOPPPP");
		$newComment->setCreatedAt(new \DateTime());
		
		$comments = $article->getComments();
		$comments[] = $newComment;
		$article->setComments($comments);
		
		$this->odm->persist($article);
                // With or without the args to flush
		$this->odm->flush(array('safe' => true));

With the above - no exception or error is thrown. It appears that the comment is added - but checking the collection in mongo and there's nothing added to the document.
Removing the PreUpdate on the Article method allows the embedded document to be saved into Article.

[MODM-55] Extract SchemaManager from DocumentManager

Mon, 23 Aug 2010 11:02:56 +0000

Extract SchemaManager from DocumentManager

[MODM-54] New console commands

Tue, 24 Aug 2010 11:58:26 +0000

We need to add commands for creating and dropping document databases and collections. I added methods to DocumentManager for creating/dropping databases and collections for documents. We have the command for creating indexes, now we need the same for databases and collections.

The reason is because you can specify configuration for the collection in the mapping that is used on collection creation:

/** @Document(collection={"name"="collname", "capped"="true", "max"="10"}) */
class Document
{}

[MODM-53] Problems with querying referenced elements

Sat, 19 Feb 2011 18:28:24 +0000

When trying to query embedded objects, I can use this syntax:

object.value = "asd"

but when I reference a different collections object, this would give me no result.

However, according to http://www.mongodb.org/display/DOCS/Schema+Design#SchemaDesign-Embedvs.Reference this should work the same way.

[MODM-52] Changes of nested embedded collection are not persisted

Wed, 18 Aug 2010 13:14:24 +0000

When there is a nested EmbedMany collection, changes of this collection are not persisted when saving root document.

Maybe simpler to explain with a test case:

/**
 * @MappedSuperClass
 */
class container
{
    /** @String */
    protected $tmp = 'ensureSaved';

    /** @EmbedMany(targetDocument="emb", cascade="all", strategy="set") */
    protected $items = array();

    function __construct($items = null) {if($items) $this->items = $items;}
    function getItems() {return $this->items;}
    function getItem($index) {return $this->items[$index];}
    function removeItem($i) {unset($this->items[$i]);}
}

/** @EmbeddedDocument */
class emb extends container
{}

/** @Document(db="tests", collection="tests") */
class doc extends container
{
    /** @Id */
    protected $id;
}

$emb = new emb(array(new emb(), new emb()));
$doc = new doc(array($emb));

$dm->persist($doc);
$dm->flush();
$dm->refresh($doc);

// change nested embedded collection:
$doc->getItem(0)->removeItem(1);
$before = count($doc->getItem(0)->getItems());

$dm->persist($doc);
$dm->flush();
$dm->refresh($doc);

$after = count($doc->getItem(0)->getItems());
var_dump($before); // outputs 1
var_dump($after);  // outputs 2, but expecting 1

[MODM-51] Strange issue with @File annotation

Wed, 18 Aug 2010 21:52:43 +0000

Not sure if it is ODM issue or some PHP Reflection issue, or I just don't getting something, but following test case won't save the file:

/** @Document(db="tests", collection="files") */
class file
{
    /** @Id */
    protected $id;

    /**
     * @File
     * @var \MongoGridFSFile
     */
    protected $file;

    function __construct($file) {$this->file = $file;}
}

$f = new file(__DIR__  . '/test.txt');
$dm->persist($f);
$dm->flush();

The problem is in annotation @var \MongoGridFSFile. Without it file is saved properly. Also, if I remove "\" in front of MongoGridFSFile, file will be also saved properly. Weird thing.

[MODM-50] GridFs file classes don't support inheritance

Tue, 17 Aug 2010 23:57:45 +0000

GridFs files do not support inheritance anymore. This issue only appeared after latest updates from git. It was working before.

Here is a test case:

/**
 * @Document(collection="files", db="tests")
 * @InheritanceType("SINGLE_COLLECTION")
 * @DiscriminatorField(fieldName="type")
 * @DiscriminatorMap({
 *      "file"="file",
 *      "image"="image"
 * })
 */
class file
{
    /** @Id */
    protected $id;

    /** @File */
    protected $file;

    function __construct($file) {$this->file = $file;}
}

/** @Document(collection="files", db="tests") */
class image extends file
{
    /** @File */
    protected $file;
}

$a = new image(__DIR__ . '/test.txt');
$dm->persist($a);
$dm->flush();

This code creates document in regular collection "files" instead of GridFs collection.

[MODM-49] Getting PHP notice and warning with empty persistent collection

Tue, 17 Aug 2010 17:16:52 +0000

If there is an object with empty collection, e.g.:

{
  "_id": "4c6a11810f9d503c03000000",
  "b": [
  ]
}

Then following code produces notice and warning:

/** @Document(db="tests", collection="tests") */
class a
{
    /** @Id */
    protected $id;

    /** @ReferenceMany(targetDocument="b", cascade="persist") */
    protected $b;

    function getB()   {return $this->b;}
}

/** @Document(db="tests", collection="tests2") */
class b
{
    /** @Id */
    protected $id;
}

$a = $dm->loadByID('a', '4c6a11810f9d503c03000000');
echo count($a->getB()); // produces notice and warning

Notice and warning text:

Notice: Undefined variable: groupedIds in library\Doctrine\ODM\MongoDB\PersistentCollection.php on line 122

Warning: Invalid argument supplied for foreach() in library\Doctrine\ODM\MongoDB\PersistentCollection.php on line 122

[MODM-48] Embedded document changes are ignored if it was empty before

Tue, 17 Aug 2010 20:13:13 +0000

Imaging the object in DB:

{
  "_id": "4c693f9f0f9d501c0d000000",
  "b": [
  ]
}

Then following code fails to update property "b":

/** @Document(db="tests", collection="tests") */
class a
{
    /** @Id */
    protected $id;

    /** @EmbedOne(targetDocument="b", cascade="all") */
    protected $b;

    function getId()  {return $this->id;}
    function getB()   {return $this->b;}
    function setB($b) {$this->b = $b;}
}

/** @EmbeddedDocument */
class b
{
    /** @String */
    protected $val;
    function setVal($val) {$this->val = $val;}
    function getVal() {return $this->val;}
}

$a = $dm->loadByID('a', '4c693f9f0f9d501c0d000000');
$a->getB()->setVal('test');

$dm->persist($a);
$dm->flush();
$dm->getUnitOfWork()->clear();

$a = $dm->loadByID('a', $a->getId());
$c = ('test' === $a->getB()->getVal());

var_dump($c); // expecting "true", but outputs false

[MODM-47] @AlsoLoad annotation, used on method causes fatal error

Tue, 17 Aug 2010 17:15:27 +0000

Getting following errors when using @AlsoLoad annotation on method:

Notice: Undefined index: isCascadePersist in library\Doctrine\ODM\MongoDB\UnitOfWork.php on line 1661

Notice: Undefined index: fieldName in library\Doctrine\ODM\MongoDB\UnitOfWork.php on line 362

Notice: Undefined index: in library\Doctrine\ODM\MongoDB\Mapping\ClassMetadata.php on line 923

Fatal error: Call to a member function getValue() on a non-object in library\Doctrine\ODM\MongoDB\Mapping\ClassMetadata.php on line 923

Test Case:

/** @Document(db="tests", collection="tests") */
class a
{
    /** @Id */
    protected $id;

    /** @String */
    protected $b = 'tmp';

    /** @AlsoLoad("c") */
    function renameC($c) {$this->b = $c;}
    function getId() {return $this->id;}
}

$a = new a();
$dm->persist($a);
$dm->flush();
$dm->getUnitOfWork()->clear();

$a = $dm->loadByID('a', $a->getId());

[MODM-46] @AlsoLoad annotation causes exception when used together with Embed/Reference annotations

Tue, 17 Aug 2010 16:57:27 +0000

Imagine that there is following object in DB:

{
  "_id": "4c6936bf0f9d50300d000000",
  "c": {
    "tmp": "tmp"
  }
}

And I want to rename property "c" to "b" in my class, using @AlsoLoad together with @EmbedOne

/** @Document(db="tests", collection="tests") */
class a
{
    /** @Id */
    protected $id;

    /**
     * @EmbedOne(targetDocument="b")
     * @AlsoLoad("c")
     */
    protected $b;
}

/** @EmbeddedDocument */
class b
{
    protected $tmp = 'tmp';
}

$a = $dm->loadByID('a', '4c6936bf0f9d50300d000000'); // will throw an exception: Property "b" in "a" was already declared, but it must be declared only once

[MODM-45] Doctrine doesn't persist empty objects

Tue, 17 Aug 2010 15:49:32 +0000

Doctrine won't persist object if it is empty (all fields are nulls). Not sure if it is bug or expected behavior, but sometimes it causes inconvenience. Test case:

/** @Document(db="tests", collection="tests") */
class a
{
    /** @Id */
    protected $id;

    /** @String */
    protected $b;
}

$a = new a();
$dm->persist($a);
$dm->flush(); // $a won't be inserted

There is also related issue: when embedding empty object (all fields are nulls) embedded object is not saved.

/** @Document(db="tests", collection="tests") */
class a
{
    /** @Id */
    protected $id;

    /** @String */
    protected $tmp = 'WorkaroundToBeSaved';

    /** @EmbedOne(targetDocument="b", cascade="all") */
    protected $b;

    function getId()  {return $this->id;}
    function getB()   {return $this->b;}
    function setB($b) {$this->b = $b;}
}

/** @EmbeddedDocument */
class b
{
    /** @String */
    protected $val;
    function setVal($val) {$this->val = $val;}
    function getVal() {return $this->val;}
}

$a = new a();
$a->setB(new b());

$dm->persist($a);
$dm->flush();
$dm->getUnitOfWork()->clear();

$a = $dm->loadByID('a', $a->getId());
$c = (null !== $a->getB()); 
var_dump($c); // returns false, while expecting true

[MODM-44] repositoryClass doesn't always get picked up for the Document Annotation

Tue, 17 Aug 2010 16:48:25 +0000

Adding the following to getRepository after the $customRepositoryClassName=..

die(print_r( array($customRepositoryClassName, $metadata),true));

Provides:

Array ( [0] => [1] => Doctrine\ODM\MongoDB\Mapping\ClassMetadata Object ( [db] => default [collection] => User [identifier] => id [file] => [indexes] => Array ( ) [name] => Bundle\DoctrineUserBundle\Documents\User [namespace] => Bundle\DoctrineUserBundle\Documents [rootDocumentName] => Bundle\DoctrineUserBundle\Documents\User [customRepositoryClassName] => [allowCustomID] => [parentClasses] => Array ( ) [subClasses] => Array ( ) [reflFields] => Array ( [id] => ReflectionProperty Object ( [name] => id [class] => Bundle\DoctrineUserBundle\Documents\User ) ) [_prototype:Doctrine\ODM\MongoDB\Mapping\ClassMetadata:private] => [inheritanceType] => 1 [fieldMappings] => Array ( [id] => Array ( [id] => 1 [fieldName] => id [name] => id [isCascadeRemove] => [isCascadePersist] => [isCascadeRefresh] => [isCascadeMerge] => [isCascadeDetach] => [type] => id [nullable] => ) ) [lifecycleCallbacks] => Array ( ) [discriminatorValue] => [discriminatorMap] => Array ( ) [discriminatorField] => [reflClass] => ReflectionClass Object ( [name] => Bundle\DoctrineUserBundle\Documents\User ) [isMappedSuperclass] => [isEmbeddedDocument] => ) )

For the following Document:

/**
 * @Document(
 *   db="account",
 *   collection="sf_doctrine_user",
 *   indexes={
 *     @Index(keys={"username"="asc"})
 *   },
 *   repositoryClass="Bundle\UserBundle\Documents\UserRepository"
 * )
 * @HasLifecycleCallbacks
 */
class User

[MODM-43] Explicit schema migration

Tue, 17 Aug 2010 16:46:39 +0000

Currently supported ways of schema migration are sufficient in many cases. But I think it's worth considering to have more explicit way to migrate schema for better readability / code maintenance.

It might be useful to be able to transform original MongoDb data prior to hydration. Maybe as a new lifecycle callback (e.g. preLoad). This way one could have special property for schema version in the document and normalize data according to version differencies. e.g.:

function preLoad(array &$data)
{
    if(!isset($data['version'])) {
        $data['version'] = 1;
    }
    switch($data['version']) {
        case 1:
             $data['fullName'] = $data['name'];
             unset($data['name']);
             // breaks are ommitted intentionally here and below
        case 2:
             $e = explode(' ', $data['fullName'])
             $data['firstname'] = $e[0];
             $data['lastname'] = $e[1];
             unset($data['fullName']);
        case 3:
             $data['address'] = array(
                 'street' => $data['street'],
                 'city' => $data['city']
             );
             unset($data['street']);
             unset($data['city']);
         case 4:
         default:
              // current version
    }
}

Just as example. It also simplifies writing tests for schema migrations as I think. Is it possible with current ODM internals? What do you think?
I could try to implement this feature if it is acceptable proposal.

[MODM-42] PersistentCollection fails when working with MongoGridFs

Tue, 17 Aug 2010 15:52:52 +0000

Getting following error when trying to use MongoGridFs files with referenceMany:

Argument 2 passed to Doctrine\ODM\MongoDB\UnitOfWork::getOrCreateDocument() must be an array, object given, called in 
D:\Work\www\syter2.localhost.dev\library\Doctrine\ODM\MongoDB\PersistentCollection.php on line 110 and defined
D:\Work\www\syter2.localhost.dev\library\Doctrine\ODM\MongoDB\UnitOfWork.php:1719

As far as I understand queries against MongoGridFS collection return instances of MongoGridFSFile, while PersistentCollection only expects arrays (as with regular collections)

I think Issue appeared after latest updates from git. Because I didn't experience it with ALPHA1 (didn't test with ALPHA2)

[MODM-41] Hydration down not work for annotation "@ReferenceMany"

Mon, 9 Aug 2010 10:03:09 +0000

When you try to find or execute query, filds with annotation reference many (arrays) do not load.

Example:

user.php

<?php

/**
 * @Document(db="DB", collection="Users")
 */
class User
{
    /**
     * @Id
     */
    public $id;
    /**
     * @String
     */
    public $name;
    /**
     * @String
     */
    public $password;
    /**
     * @String
     */
    public $email;
        /**
     * @ReferenceMany(targetDocument="Group")
     */
    public $groups = array();
}
?>

group.php

<?php

/**
 * @Document(db="MCI", collection="Groups")
 */
class Group
{
    /**
     * @Id
     */
    public $id;
    /**
     * @String
     */
    public $name;
    /**
     * @String
     */
    public $role_name;

}
?>

When you execute this line:

 $obj = $this->dm->findOne("User",("name" => "Flavio"));

All the fields are returned correctly, but "groups" apear empty.

When you use @EmbedMany annotation works file.

Regards.

PS: I'm using codeigniter framework

[MODM-40] Move value scalarization and comparison to Unit Of Work

Fri, 6 Aug 2010 22:11:17 +0000

The BasicDocumentPersister::_equals belongs in the UnitOfWork.

[MODM-39] Update project description on the projects page

Tue, 17 Aug 2010 15:52:27 +0000

The projects page http://www.doctrine-project.org/projects says that ODM MongoDB is for PHP 5.3.0, whereas it really is for PHP 5.3.2+, as far as I know.

[MODM-38] Using YAML description with embedMany causes PHP notice error

Fri, 6 Aug 2010 17:06:13 +0000

When using the YAML style description together with the new embedMany functionality of mixed documents, you get a PHP notice error every time you create a new model.

Because when you have mixed documents, you don't specify a targetDocument, and therefore the YAML Driver can not find an element in the array that describes the targetDocument.

[MODM-37] Problems with EmbedMany and discrimatorMap and discriminatorField

Fri, 6 Aug 2010 17:09:14 +0000

I'm experiencing a problem when trying to embed documents and specify my own discriminatorMap and Field.

This is the code I have:

    /** @Document(collection = "ticket") */
    class App_Model_Ticket extends App_Model_Abstract
    {
    	/**
    	 * @EmbedMany(
    	 *	discriminatorField = "type",
    	 *	discriminatorMap={
    	 *		"twitter"="App_Model_Ticket_Twitter",
	 *		"email"="App_Model_Ticket_Email"
	 *	})
	 */
    	protected $messages = array();
    
    	// [...]
    }

App_Model_Abstract is a MappedSuperClass.

App_Model_Ticket_Email and App_Model_Ticket_Twitter pretty much look alike right now:

    /** @EmbeddedDocument */
    class App_Model_Ticket_Email extends App_Model_Ticket_Message
    {
    }

and App_Model_Ticket_Message is another MappedSuperClass that extends App_Model_Abstract.

Now, whenever I create a new model and persist it to mongoDB, the entry gets created and looks like this:

    [_id] => MongoId Object (
    )
    [messages] => Array (
        [0] => Array (
            [message] => Lorem ipsum
            [subject] => Ich bin ein Berliner22
            [dateSent] => MongoDate Object (
                [sec] => 1280909855
                [usec] => 0
            )
            [_doctrine_class_name] => App_Model_Ticket_Twitter
        )
        [1] => Array (
            [message] => Lorem ipsum
            [subject] => Ich bin ein Berliner22
            [dateSent] => MongoDate Object (
                [sec] => 1280909855
                [usec] => 0
            )
            [_doctrine_class_name] => App_Model_Ticket_Email
        )
    )
    [subject] => Ich bin ein Berliner22
    [dateCreated] => MongoDate Object (
        [sec] => 1280909855
        [usec] => 0
    )
    [dateLastMessage] => MongoDate Object (
        [sec] => 1280909855

However, as you can see no type field for my embedded documents, it still uses _doctrine_class_name.

But when I try to fetch this object, I get an exception saying "Class not found".

I think this is because right now Doctrine ODM does not write into the custom discriminatorField with embedded documents, but reads from it.

[MODM-36] Embedded relations are not persisted after a flush()

Fri, 6 Aug 2010 17:01:41 +0000

Newly added embedded relations do not get persisted when a flush() is executed before they are added to the parent document. Here is a failing test, note the comment "// Adding this flush here makes level1 not to be inserted.":

public function testFlushEmbedded()

{ $test = new EmbeddedTestLevel0(); $test->name = 'test'; $this->dm->persist($test); $this->dm->flush(); $this->dm->clear(); $test = $this->dm->findOne('Documents\Functional\EmbeddedTestLevel0'); $this->assertInstanceOf('Documents\Functional\EmbeddedTestLevel0', $test); // Adding this flush here makes level1 not to be inserted. $this->dm->flush(); $level1 = new EmbeddedTestLevel1(); $level1->name = 'test level1 #1'; $test->level1[] = $level1; $this->dm->persist($test); $this->dm->flush(); $this->dm->clear(); $test = $this->dm->findOne('Documents\Functional\EmbeddedTestLevel0'); $this->assertInstanceOf('Documents\Functional\EmbeddedTestLevel0', $test); $this->assertInstanceOf('Documents\Functional\EmbeddedTestLevel1', $test->level1[0]); }

[MODM-35] Proxy item gets reset on persistent collection load if that item was in the collection

Fri, 6 Aug 2010 22:13:51 +0000

Proxy item gets reset on persistent collection load if that item was in the collection

[MODM-34] Custom Id always gets sent with changeset

Fri, 6 Aug 2010 23:15:38 +0000

Whenever the Unit of Work computes the changeset for a document with custom id, the id attribute always gets sent.

[MODM-33] Class-level annotations are ignored if set on MappedSuperclass

Fri, 6 Aug 2010 23:51:42 +0000

Class-level annotations: @HasLifecycleCallbacks, @InheritanceType, @DiscriminatorField, @DiscriminatorMap have no effect when defined on @MappedSuperclass

You must explicitly set @HasLifecycleCallbacks for every document class to make callback work. As for inheritance annotations, you have to copy-paste all annotations to all document classes to make it work.

Simple example:

/**
 * @MappedSuperclass
 * @HasLifecycleCallbacks
 */
abstract class a
{
    /** @String */
    protected $a = '';

    /** @PrePersist */
    function prePersist() {$this->a = 'a';}
}

/** @Document(db="tests",collection="tests") */
class b extends a
{}

$b = new b();
$dm->persist($b);
$dm->flush($b);

With this example prePersist won't be called. Not sure if it is bug or expected behavior, but it adds some inconvenience, especially with inheritance mapping.

[MODM-32] dbref $id persisted as string instead of objectid

Fri, 6 Aug 2010 22:09:43 +0000

A clone of http://github.com/doctrine/mongodb-odm/issues/issue/2/.

[MODM-31] Cannot use a document against multiple classes

Fri, 30 Jul 2010 13:27:17 +0000

It would be useful to be able to use two classes on one document, in a way that transparently extends the original schema. My use case:

I have a base Application that manages users of the system. A module/plugin to the system wants to extend the User records to include references to one of it's documents:

namespace Application\Model;
class User {
//user properties here
}

...

namespace Organisation\Model;
use Application\Model\User as BaseUser;

class Organisation {
//organisations properties
}

class User extends BaseUser {
/** @ReferenceOne(targetDocument="\Organisation\Model\Organisation") */
protected $organisation
}

It this theoretical scenario, the original \Application\Model\User needs to be used by the base application, but the \Organisation\Model\User can be used by the addon module to transparently add more data to the same user. The base class doesn't need to know it will be used this way.

Current behaviour for the above will ignore the additional properties not available in the parent class, and doesn't throw any exceptions/errors.

Other ways to make it work involve the base class knowing it will be extended via SCI, or using a mappedsuperclass?, which isn't transparent in the base class, it needs to be altered to work with it's children.

[MODM-30] yaml lifecycleCallbacks param expects an array not string

Tue, 27 Jul 2010 10:23:51 +0000

In the manual, when configuring lifecycleCallbacks

  lifecycleCallbacks:
    doStuffOnPrePersist: prePersist
    doStuffOnPostPersist: postPersist

it seems, that event name must be the key not the value

  lifecycleCallbacks:
    prePersist: doStuffOnPrePersist
    postPersist: doStuffOnPostPersist

and when parsing it is expecting an array not a string

maybe a fix would be :

// Doctrine/ODM/MongoDB/Mapping/Driver/YamlDriver.php  line 123
if (isset($element['lifecycleCallbacks'])) {
            foreach ($element['lifecycleCallbacks'] as $type => $methods) {
if(!is_array($methods)){
$methods = array($methods);
}
                foreach ($methods as $method) {
                    $class->addLifecycleCallback($method, constant('Doctrine\ODM\MongoDB\ODMEvents::' . $type));
                }
            }
        }

[MODM-29] Persisting changes ordering of elements in embedded collection in some cases

Thu, 19 Aug 2010 03:54:56 +0000

After changing ordering of elements in collection, it is persisted incorrectly (with different ordering than expected).

Here is a test case:

/** @Document(collection="tests", db="tests") */
class doc
{
    /** @Id */
    protected $id;

    /** @EmbedMany(targetDocument="emb") */
    protected $collection;

    function __construct($c) {$this->set($c);}

    function set($c) {$this->collection = $c;}
    function get() {return $this->collection;}
}

/** @EmbeddedDocument */
class emb
{
    /** @String */
    protected $val;

    function __construct($val) {$this->val = $val;}
    function get() {return $this->val;}
}

$collection = new ArrayCollection(array(
    new emb('0'),
    new emb('1'),
    new emb('2')
));

// TEST CASE:
$doc = new doc($collection);

$dm->persist($doc);
$dm->flush();

// place element '0' after '1'
$collection = new ArrayCollection(array(
    $collection[1],
    $collection[0],
    $collection[2]
));

$doc->set($collection);

$dm->persist($doc);
$dm->flush();

$dm->refresh($doc);

foreach($doc->get() as $value) {
    echo $value->get() . "\n";
}

// expecting: 
// 1
// 0
// 2

// getting: 
// 2
// 1
// 0

Is it an issue? Or is it supposed that ordering should be resolved in application code?

[MODM-28] xml mapping : embedded-document node is ignored, can't persist

Tue, 27 Jul 2010 10:55:23 +0000

 
//file Doctrine/ODM/MongoDB/Mapping/Driver/XmlDriver.php line 171

protected function _loadMappingFile($file)
    {
        $result = array();
        $xmlElement = simplexml_load_file($file);

        if (isset($xmlElement->document)) {
            foreach ($xmlElement->document as $documentElement) {
                $documentName = (string) $documentElement['name'];
                $result[$documentName] = $documentElement;
            }
        }
        
        return $result;
    }

embedded-document and mapped-superclass are ignored so embed documents are not persisted

[MODM-27] It would be great to have a way to use different collection classes with referencing/embedding

Thu, 22 Jul 2010 23:17:59 +0000

Currently ODM creates an instance of ArrayCollection for every referenced/embedded collection.

It would be great, if there was a way to specify which collection class should be actually used. Imagine simple use-case: one have created class TagsCollection extends ArrayCollection with __toString method, which automatically transforms collection of tags to comma-separated tags string.

Would it be possible to have e.g. @EmbedMany(collection="TagsCollection") ?

[MODM-26] MongoCursor doesn't implement Countable interface

Mon, 19 Jul 2010 13:09:48 +0000

this causes confusion when query returns empty array instead of MongoCursor object, meaning you can't use neither count($result) nor $result->count(), and have to check for the returned type explicitly

[MODM-25] AnnotationDriver.php Line 175

Mon, 19 Jul 2010 14:28:20 +0000

$mapping['fieldName'] should be replace with something else.
Maybe create a whole new metadata property, or map load methods as onLoad lyfecycle events...

[MODM-24] Hydratation of extra fields

Mon, 19 Jul 2010 23:15:39 +0000

I'm working on a project using MongoDB with ODM especially for the schemaless features.
So I have one collection with some default fields in my base class.
Every inherited class add fields but we're still in the same collection.

First, prior to save the document, I add the new mappings (imported from the inherited class) so they will be saved in the database. This part works fine.
The problem is that when the ODM hydrates the documents, it sticks to the $metadata->fieldMappings defined by the base class, and ignore the others.

I've made a quick patch for that, but it doesn't make any type cast, I didn't inspect the code deep enough to make it better.

In the Doctrine\ODM\MongoDB\Hydrator class (line 73) :

    public function hydrate(ClassMetadata $metadata, $document, $data)
    {
        $values = array();

        // Patch
        foreach ($data as $field => $value)
        {
          if(!array_key_exists($field, $metadata->fieldMappings))
          {
            $document->$field = $value;
          }
        }
        // end Patch

        foreach ($metadata->fieldMappings as $mapping) {
[...]

[MODM-23] Embeded objects gets doubled [see description for the whole scenario]

Tue, 13 Jul 2010 10:41:51 +0000

If you have the database structure as:
'Group' Collection has 'tables' (ReferenceMany targetDocument="Documents\Table") and 'chairs' (ReferenceMany targetDocument="Documents\Chair").
'Table' Collection has 'glasses' (EmbedMany targetDocument="Documents\Glass") and a name as (@String).
'Chair' Collection has a name as (@String) and tablenames as (@Hash).
'Glass' Collection has name as (@String).

First, I simply add a glass to table and add that table to group. And create a chair and add it to group also.
$dm = $this->doctrine->getDM();
$group = new Group();
$table = new Table();
$chair = new Chair();
$glass = new Glass();

$group->tables[] = $table;
$group->chairs[] = $chair;
$table->glasses[] = $glass;

$dm->persist($group);
$dm->flush();
*At this point the tablenames in 'Chair' collection is not entered.

Now I call a function, which adds a new chair;
function addChair()
{
$dm = $this->doctrine->getDM();
$chair = new Chair();
$group = $dm->createQuery('Documents\Group')
->where('name','group')
->getSingleResult();
foreach($group->tables as $table)

{ $chair->tableNames[] = $table->name; }

$group->chairs[] = $chair;
$dm->persist($chair);
$dm->flush();
}

and as mentioned I traverse on tables to get table names and add those name in a new 'Chair' Collection's tablenames (@Hash).

Now in Db I have:
a group with two chairs and a table (both Referenced).
two chairs (one with an array of "tablenames" and one doesn't have "tablenames"),
a table with "TWO" embedded glasses <<--this is very strange I never added another glass to table!!!!

Note: As I call "addChair()" one more time the glasses in table get multiplied by two!!!
Please fix this asap.
Thanks
Regards
Ahsan

[MODM-22] Document incorrectly scheduled for update

Mon, 19 Jul 2010 23:52:55 +0000

I have the following documents:

Product:
product_id
sellable (dbref)

Sellable:
product (dbref)
seller (dbref)

Seller:
name

If I create a new Sellable for a seller the seller gets scheduled for update even if nothing has changed.The document persister correctly doesn't try to actually execute the update but Lifecycle events still get called. The flow is:

1. Schedule for update
2. Call _executeUpdate
3. Call preUpdate
4. Call BasicDocumentPersister::update(), which does nothing because of no actual changes
5. Call postUpdate.

preUpdate and postUpdate being called when there's no actual changes is causing problems. It seems like the proper course of action would be to either not schedule the document for update or check if there's any actual changes before calling preUpdate and postUpdate.

[MODM-21] AnnotationDriver doesn't allow custom types

Mon, 19 Jul 2010 15:01:15 +0000

Right now AnnotationDriver.php does not allow you to create custom types. You can with YAML and XML but the $types array on line ~142 of AnnotationDriver.php is hard coded so there's no way to get a custom type in there.

[MODM-20] SINGLE_COLLECTION inheritance does not work

Wed, 24 Nov 2010 13:10:19 +0000

It seems that SINGLE_COLLECTION inheritance is not implemented?

Method UnitOfWork::getOrCreateDocument calls Mapping\Metadata::newInstance without taking possible discriminator map into account.

The example in the official documentation (http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/reference/inheritance-mapping/en) is not a real test: the object is first created as a child-class instance before being queried through the parent class, so the object is returned without hydration, from the UnitOfWork identityMap cache.

The corresponding code from Doctrine\ORM is in Doctrine\ORM\Internal\Hydration\ObjectHydrator::_getEntity (find class name through discriminator map, if any).

[MODM-19] Field annotation missing "name" support

Mon, 19 Jul 2010 15:51:10 +0000

Documentation states that field names can be overriden by using a "name" parameter but Doctrine throws exception.
Also there is a missing comma in the documentation between the type and name params.

From documentation:

http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/reference/annotations-reference/en#ann_field

Unable to find source-code formatter for language: php. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

/**
 * @Field(type="string" name="origin")
 */
protected $country;

My source code:

Unable to find source-code formatter for language: php. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

    /**
     * @Field(type="string", name="password")
    **/
    protected $_password;

Exception:

BadMethodCallException:
Unknown property 'name' on annotation 'Doctrine\ODM\MongoDB\Mapping\Field'.

[MODM-18] All Document object properties are persisted regardless of mapping instructions.

Tue, 13 Jul 2010 10:42:43 +0000

User Model

class Users_Model_User
{
    public $id;
    public $username;
    public $password;
    public $myRuntimeProperty = 'some value';
}

Document Mapping (in YAML)

Users_Model_User:
db: my_db
collection: users
fields:
    id:
        fieldName: id
        id: true
    username:
        fieldName: username
        type: string
    password:
        fieldName: password
        type: string

My test code

$user = new Users_Model_User;
$user->username = 'hello';
$user->password = 'world';
$this->dm->persist($user);
$this->dm->flush();

The result is "myRuntimeProperty" is saved to the db.
This causes problems for several properties such as "_propertyChangedListeners" which, once saved and later loaded back from the database, overrides the array of object listeners with a string of "Array"

If this is not a bug:
I have search everywhere for an answer. All the docs, mailing list, irc, blogs. If this is not a bug the solution needs to be better documented.

Temporary fix:
Use Docblock Annotations, set the unwanted properties with @NotSaved
(Unless there is also a way to set NotSaved using YAML?)

[MODM-17] Multiple array / object with same content/properties do not get persisted

Mon, 19 Jul 2010 17:13:16 +0000

If I have a Collection field and try to add 2 values that are the same, the second value never gets saved to the document. Example code:

class User
{
  /** @Id */
  private $id;

  /** @String */
  private $name;

  /** @Collection */
  private $logs = array();

}

    $o = $dm->findOne(':User', array('name' => $arguments['name']));

    $found = true;

    if (!$o) {
      $found = false;
      $o = new User();
    }

    $o->setName($arguments['name']);

    $o->addLog( array('a' => 'b' ));

    $dm->persist($o);

    $dm->flush();

or a EmbeddedMany field, and try to add to add 2 objects with the same content the same thing happens:

class User
{
  /** @Id */
  private $id;

  /** @String */
  private $name;

  /** @EmbedMany(targetDocument="UserLog") */
  private $logs = array();
}

    $o = $dm->findOne(':User', array('name' => $arguments['name']));

    $found = true;

    if (!$o) {
      $found = false;
      $o = new User();
    }

    $o->setName($arguments['name']);

    $l = new UserLog();

    $l->setMsg('Testing');

    $o->addLog($l);

    $dm->persist($o);

    $dm->flush();

If I change $l->setMsg('Testing'.time());

then it adds all the instances.

[MODM-16] loadById failing on custom ids

Thu, 17 Jun 2010 09:11:33 +0000

DocumentManager::loadByID is failing on custom ids right now because it's checking for the custom id flag on the metadata and converting to \MongoID. It should probably be using the new $class->getPHPIdentifierValue method instead.

[MODM-15] addWhere

Tue, 15 Jun 2010 12:09:20 +0000

After removing addWhere http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/reference/query-builder-api/en#addWhere should be updated.
$query = $dm->createQuery('User')
->where('type', 'admin')
->where('active', 1);
like this, right?

http://github.com/doctrine/mongodb-odm/blob/master/lib/Doctrine/ODM/MongoDB/Query.php#L313
Is at least missleading.

Thanks for the great work!

[MODM-14] Default database when @Document annotation does not contain a db attribute.

Fri, 11 Jun 2010 15:06:46 +0000

When a Document is annotated with @Document(collection="test") and is missing the db attribute the ODM defaults to mongo_dev. What i expected was it defaulted to the database name given when creating a connection.

[MODM-13] Problems with merge()

Thu, 10 Jun 2010 09:00:24 +0000

while doing a merge, I got some PHP errors.
Seems like these steps fix the problem:
1. Change line 1215 of UnitOfWork.php to
$id = $class->getIdentifierValue($document);
it was ValueS before

2. in function _cascadeMerge starting in line 1464 of UnitOfWork.php
change the inner calls from:
$this->_cascadeMerge($relatedDocument, $visited);
To:
$this->_cascadeMerge($relatedDocument, $managedCopy, $visited);

I didn't look deeper into ODM, just tried this to things and it seems to work now, so please excuse if it's bs ...

[MODM-12] Undefined variable error

Wed, 9 Jun 2010 19:55:06 +0000

In UnitOfWork::_computeAssociationChanges there are several references to $document but $document is never declared in that method, or passed into it. From looking at ORM it looks like $entry is the right variable to be using here.

[MODM-11] Allow custom persisters

Wed, 9 Jun 2010 19:55:48 +0000

I'm trying to write a SoftDelete extension for Doctrine ODM but am unable to do so because I need to be able to either use my own, custom, Persister or my own, custom, MongoCollection proxy. Providing a custom persister seems like the way to go as it opens up the flexibility of creating other behaviors (such as a Paginator).

[MODM-10] Missing use statement in UnitOfWork

Wed, 9 Jun 2010 19:50:51 +0000

The UnitOfWork.php class has several references to LifecycleEventArgs but has no 'use' statement for it. This causes syntax errors when trying to use lifecycle events.

[MODM-9] Unexpected: MappedSuperclass private property without annotation becomes persisted

Wed, 9 Jun 2010 19:50:37 +0000

/** @MappedSuperclass */
class Model {

    private $errors = array();

    protected function getErrors() {
        return $this->errors;
    }
}

/**
 * @Document(db="mydb", collection="data")
 */
class Data extends Model {
    /**
     * @Id
     */
    public $id;

    /**
     * @String
     */
    public $name;
}

Did not expect, that $errors goes into mongo.

[MODM-8] custom repositories don't work when setting MetadataCacheImpl

Mon, 2 Aug 2010 17:27:24 +0000

When I enable metadataCache:

$config->setMetadataCacheImpl(new \Doctrine\Common\Cache\ApcCache());

My custom repository stops working. For I example I have a method findAllAssoc.
witout enabling metadata cache it works fine.

Fatal error: Uncaught exception 'BadMethodCallException' with message 'Undefined method 'findAllAssoc'. The method name must start with either findBy or findOneBy!' in /data/sites/mongodb_odm/lib/Doctrine/ODM/MongoDB/DocumentRepository.php:197
Stack trace:
#0 [internal function]: Doctrine\ODM\MongoDB\DocumentRepository->__call('findAllAssoc', Array)
#1 /data/sites/cms.enkorting.nl/application/modules/user/controllers/IndexController.php(72): Doctrine\ODM\MongoDB\DocumentRepository->findAllAssoc()

Cheers, Onno

[MODM-7] Fatal error when using a custom repository class in AnnotationDriver

Wed, 9 Jun 2010 19:50:01 +0000

When defining a custom repository in an annotation the AnnotationDriver gives an Fatal error on line 105

Call to a member function setCustomRepositoryClass() on a non-object in /data/sites/lib/Doctrine/ODM/MongoDB/Mapping/Driver/AnnotationDriver.php on line 105

replacing:
$metadata->setCustomRepositoryClass($documentAnnot->repositoryClass);

for:
$class->setCustomRepositoryClass($documentAnnot->repositoryClass);

solves this issue..
Cheers, Onno

[MODM-6] Error In Documentation

Wed, 9 Jun 2010 19:49:49 +0000

@see http://www.doctrine-project.org/projects/mongodb_odm/1.0/docs/cookbook/getting-started/en

The Doctrine\Common\Annotations\AnnotationReader requires an instance Doctrine\Common\Cache\Cache to be passed to it on construction. In the documentation above it is constructed with no such instance.

Regards,

Sam

[MODM-5] Make embedding work on objects in a collection inheritance tree

Wed, 9 Jun 2010 19:49:27 +0000

https://gist.github.com/72a8e30931eb56dd84bc

[MODM-4] tweak xml/yml syntax

Wed, 9 Jun 2010 19:48:57 +0000

[15:00] <jwage> we need to write the schema file for the xml
[15:00] <jwage> and maybe expand the xml and yaml syntax
[15:00] <jwage> to have <reference
[15:00] <jwage> <embedded
[15:00] <jwage> etc
[15:00] <avalanche123> ah, I see, to make it more like ORM?
[15:01] <jwage> i think so
[15:01] <jwage> it's just better
[15:01] <jwage> you dont have to specify embedded=true
[15:01] <avalanche123> right
[15:01] <jwage> when reading in the <embedded you will just set that
[15:01] <jwage> in the array

[MODM-3] API design

Wed, 9 Jun 2010 19:48:43 +0000

I know I am nit-picky, I'm really just trying to help, but I think methods like save() that were recently added are just API bloat since all it does is persist + flush. The naming is also confusing, having both save and persist. If you really want to add a method to the public API to exchange 2 lines in user code against 1 line, then at least a more descriptive name would be better, like persistAndFlush().

API design is difficult, don't take it too lightly (thats what php did, heh)

[MODM-2] Reconsider the naming

Wed, 9 Jun 2010 19:48:14 +0000

We may want to reconsider the naming of things in ODM projects. I know the term "entity" is heavily overloaded but I think there might be a misunderstanding here of what @Entity refers to in the ORM. The ORM @Entity actually means a (relational) database entity (entity relationship diagram, etc...) not the "DDD" entity, of course there are many similarities.

I don't feel that comfortable with the possibility of half a dozen different "EntityManager"s, especially if they represent entirely different storage paradigms.

Remember, @Entity does not really mean "DDD entity". An EntityManager is not a "DDD entity manager" It is part of the infrastructure (persistence), not of the domain model.

Do we want X different "EntityManager"s? When considering that @Entity actually refers to a relational database entity, it would make more sense to call these things @Document in the ODM projects, since that is what they're stored as. Then we could instead use the term DocumentManager, and not EntityManager for the ODM projects.

I realize that this confusion comes from the fact that many think "entity" = "DDD entity" but that is not the case. @Entity in the ORM refers to a relational database entity just like @Column refers to a relational database column.

So my vote currently absolutely goes for @Document and DocumentManager to keep things consistent. Of course, a mongo and a couch project can both have a DocumentManager, that is fine, both storage paradigms are documents.

[MODM-1] Using Doctrine\Common\Collections\Collection

Wed, 9 Jun 2010 19:47:41 +0000

Collections of objects in mongodb entities/documents should be handled like in the ORM through the Common collections.
This makes it possible to use similar transparent lazy-loading strategies, without $em->loadEntityAssociations which is contrary to the idea of transparent persistence.
Also this would make mongo entities/documents compatible with orm/relational entities, that is, using the same class(es) as a mongo and orm entity.

This goes for other potential upcoming projects, like couchdb, too. We should always encourage the use of the Doctrine Common collections in domain models.

[DWEB-111] http://wiki.doctrine-project.org/ not working

Wed, 12 Dec 2012 13:29:14 +0000

return a 500 the last few Days