• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Many to many relationship... some problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Many to many relationship... some problem


  • Subject: Re: Many to many relationship... some problem
  • From: Amedeo Mantica <email@hidden>
  • Date: Mon, 3 Aug 2009 18:29:27 +0200

why do you want to put the quantity in that table ???

leave the relationship alone

create a table " cart " with a relationship to product and a column quantity.

then create a relationship cart to order

Regards
Amedeo

On 03/ago/09, at 18:16, Francesco Romano wrote:

On 03/ago/09, at 18:04, Lachlan Deck wrote:

On 04/08/2009, at 1:39 AM, Francesco Romano wrote:

On 03/ago/09, at 16:10, Lachlan Deck wrote:

On 03/08/2009, at 7:21 PM, Francesco Romano wrote:

Hi..
I'm having some problem with a many-to-many relationship.
I've two entities: Order and Product.
They have a many-to-many relationship, and an attribute: quantity.
The strange thing is that I don't see the OrderProduct model generated...

Check the value of Class Name in the model. It's probably EOGenericRecord. Change it to you.model.OrderProduct

You are right.. Now I see the class


Well.. to be honest I don't understand how many-to-many works... (In WO.. I know the "DB-theory")...

OrderProduct orderProduct = (OrderProduct)EOUtilities.createAndInsertInstance(ec, OrderProduct.ENTITY_NAME);
// or
OrderProduct orderProduct = OrderProduct.createOrderProduct(ec, product, order);
orderProduct.setQuantity(quantity);


ec.saveChanges();

Little problem.. the only method createOrderProduct has as arguments: editingContext, quantity.

1) Your OrderProduct should (usually) have a compound primary key. (orderID, productID). Both keys shouldn't allow null. Both relationships (order, product) should be manditory. Then regenerate your class.

I attach an image.. it's the OrderProduct entity. <Picture 1.png>

So.. I can't set it's pks.

2) This is good. :-) You're dealing with objects now, not database artifacts like pks and foreign keys. You'll be setting object relationships not pk/fk relationships.


Simply fetch the product/order _objects_ and
orderProduct.setOrder(order);
orderProduct.setProduct(product);


With pks I meant that I don't have the setProduct and setOrder method (and in the constructor).


with regards,
--

Lachlan Deck


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Many to many relationship... some problem (From: Francesco Romano <email@hidden>)
 >Re: Many to many relationship... some problem (From: Lachlan Deck <email@hidden>)
 >Re: Many to many relationship... some problem (From: Francesco Romano <email@hidden>)
 >Re: Many to many relationship... some problem (From: Lachlan Deck <email@hidden>)
 >Re: Many to many relationship... some problem (From: Francesco Romano <email@hidden>)

  • Prev by Date: Re: Many to many relationship... some problem
  • Next by Date: Service return limited to 100
  • Previous by thread: Re: Many to many relationship... some problem
  • Next by thread: Re: Many to many relationship... some problem
  • Index(es):
    • Date
    • Thread