Thanks.
I have tried the new DQL and results are as follows:
- I now have a one-dimensional array with 4 indices, each holding the
"Item" Entity
- One "Product" entity is loaded as part of the above entity (one for
each index location), under "product" member variable.
- The
I found this:
http://pietervogelaar.nl/doctrine-2-use-foreign-key-as-field-in-dql
The posts in the link are from 2-3 years ago and recommend using an
IDENTITY function. I am curious if using IDENTITY is still a recommended
practice?
I find it that in some of my code I have been unwittingly
I am working with a legacy codebase, and a database that has no foreign key
constraints defined, nor has referential integrity.
And what I'm doing is I am modeling my Doctrine entities in PHP to match
MySQL tables, so that I can use Doctrine inside PHP code.
And so first I build my Entities to
id;
}
/**
* Set name
*
* @param string $name
*
* @return tesst
*/
public function setName($name)
{
$this->name = $name;
return $this;
}
/**
* Get name
*
* @return string
*/
public function getName()
>
>
>
Am Montag, 16. Mai 2016 12:21:19 UTC+2 schrieb Marco Pivetta:
>
> Seems like you mis-configured your metadata drivers.
>
> Also: why do you need to generate entities, if you already wrote the
> entity's code?
>
> Marco Pivetta
>
> http://twitter.com/Ocramius
>
>
Seems like you mis-configured your metadata drivers.
Also: why do you need to generate entities, if you already wrote the
entity's code?
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
On 16 May 2016 at 12:18, wrote:
>
> namespace
id;
}
/**
* Set name
*
* @param string $name
*
* @return Products
*/
public function setName($name)
{
$this->name = $name;
return $this;
}
/**
* Get name
*
* @return string
*/
public function