A @Column can be *nullable*: determines if NULL values allowed for this column. Other possibilities: use a NULL-object (a no-order Order) or make the orders recurring, so that the invoices always match an order.
On Sunday, 4 May 2014 12:42:25 UTC+2, Parsifal wrote: > > The association from Order to Invoice is obviously OneToMany because of > recurring invoices, and for adding a new entity for invoice, first the > order object should be loaded as stated in wiki, most softwares has the > ability to issue a standalone invoice to clients in admin area, without an > actual order. They are able to do so becuase they are not using doctrine, > they are just using db tables. > I guess this is not possible to generate a new invoice without order with > doctrine as this is ManyToOne to order entity? Is there any trick or > suggestion to do so? > > > > > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
