Repeat group

Ajyamal

New Member
hi

When I edit a record on a repeated group (either joins), new record would be created.
I think the history record almost does not needed.

Now:
add and edit => update statement

Shousd be ? :

add => update statement
edit => replace statement
 
I'm really not sure what you mean.

Can you record a Jing screencast to demonstrate what you mean, or include some screenshots?

-- hugh
 
[thread=16609]I wanted to say this on a sight of sql language[/thread]

And I thought :

(PK)table-A ---- 1:n ---- table-B (FK)

this table-B has also (PK) and the order.
I thought this order woud be pain.

And, the PK must be required the uniq but not order when table has joined.
And if it is needed an order, table-b might have second PK for ordering.
And I knew that php can make uniq key like
Code:
<?php
	echo md5(uniqid(rand(),1));
?>
this can make an uniq but not ordered.

I just talk about my opinion. thank u.
 
not sure why you would insist on the primary key being used for the ordering?
It makes more sense to add a new field to store any user assigned order.
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top