doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-24 06:52:09 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

[PR #348] [CLOSED] [DDC-1819][WIP] Arbitrary object hydrator #8064

New Issue
Open
opened 2026-01-22 15:58:13 +01:00 by admin · 0 comments
admin commented 2026-01-22 15:58:13 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/doctrine/orm/pull/348
Author: @marijn
Created: 5/14/2012
Status: ❌ Closed

Base: master ← Head: DDC-1819-arbitrary-object-hydrator

📝 Commits (3)

  • 1038547 Add models for testing arbitrary object hydration.
  • a6e2548 Add arbitrary object hydration test suite.
  • a2f9bc0 Add class for hydrating arbitrary objects.

📊 Changes

7 files changed (+314 additions, -0 deletions)

View changed files

📝 lib/Doctrine/ORM/AbstractQuery.php (+5 -0)
📝 lib/Doctrine/ORM/EntityManager.php (+3 -0)
➕ lib/Doctrine/ORM/Internal/Hydration/ArbitraryObjectHydrator.php (+54 -0)
➕ tests/Doctrine/Tests/Models/DDC1819/DataTransferObject/CustomerAddressView.php (+52 -0)
➕ tests/Doctrine/Tests/Models/DDC1819/Entity/Address.php (+71 -0)
➕ tests/Doctrine/Tests/Models/DDC1819/Entity/Customer.php (+44 -0)
➕ tests/Doctrine/Tests/ORM/Hydration/ArbitraryObjectHydratorTest.php (+85 -0)

📄 Description

Initial work (in progress) on a test suite for the arbitrary object hydrator, as discussed in DDC-1819. Any tips are appreciated. I'm not too sure what the test suite should and should not cover.

Other questions I have include:

  1. Should the HYDRATE_ARBITRARY_OBJECT constant be added to the AbstractQuery class or the NativeQuery class? It only makes sense in the former but it might be missed when more constants are added in the future...
  2. Should I use data providers in my tests for the result set data?
  3. Should my tests be added to a DDC1819 namespace?
  4. Should I add functional tests?

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/doctrine/orm/pull/348 **Author:** [@marijn](https://github.com/marijn) **Created:** 5/14/2012 **Status:** ❌ Closed **Base:** `master` ← **Head:** `DDC-1819-arbitrary-object-hydrator` --- ### 📝 Commits (3) - [`1038547`](https://github.com/doctrine/orm/commit/1038547479658c28a60795ed0d35566049bbf2d3) Add models for testing arbitrary object hydration. - [`a6e2548`](https://github.com/doctrine/orm/commit/a6e25484f8f8ace0892ea4d2d0dfd6d29b156a82) Add arbitrary object hydration test suite. - [`a2f9bc0`](https://github.com/doctrine/orm/commit/a2f9bc04b2e276fb6c813da50f0a4239a2e38322) Add class for hydrating arbitrary objects. ### 📊 Changes **7 files changed** (+314 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `lib/Doctrine/ORM/AbstractQuery.php` (+5 -0) 📝 `lib/Doctrine/ORM/EntityManager.php` (+3 -0) ➕ `lib/Doctrine/ORM/Internal/Hydration/ArbitraryObjectHydrator.php` (+54 -0) ➕ `tests/Doctrine/Tests/Models/DDC1819/DataTransferObject/CustomerAddressView.php` (+52 -0) ➕ `tests/Doctrine/Tests/Models/DDC1819/Entity/Address.php` (+71 -0) ➕ `tests/Doctrine/Tests/Models/DDC1819/Entity/Customer.php` (+44 -0) ➕ `tests/Doctrine/Tests/ORM/Hydration/ArbitraryObjectHydratorTest.php` (+85 -0) </details> ### 📄 Description Initial work (in progress) on a test suite for the arbitrary object hydrator, as discussed in [DDC-1819](http://www.doctrine-project.org/jira/browse/DDC-1819). Any tips are appreciated. I'm not too sure what the test suite should and should not cover. Other questions I have include: 1. Should the `HYDRATE_ARBITRARY_OBJECT` constant be added to the `AbstractQuery` class or the `NativeQuery` class? It only makes sense in the former but it might be missed when more constants are added in the future... 2. Should I use data providers in my tests for the result set data? 3. Should my tests be added to a `DDC1819` namespace? 4. Should I add functional tests? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
admin added the pull-request label 2026-01-22 15:58:13 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#8064
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?