On Thu, 9 Feb 2012 19:58:21 +0530, Vineet Deodhar

<vineet.deodhar@gmail.com> wrote:

>

>In GrandChildTable,

>user deletes 2nd row.

>updates 1st row.

>Beforehand, I, of course, do not know what the user will do with records

>(update or delete).

>I know how to call the methods like new(), save(), delete(), seek() &

>setFieldVal() individually on table records.

>

<snip>

>Otherwise I need to trace-out the records where data was there before

>user-interaction, and the data is absent after user-interaction.

My apologies, I don't have any experience directly with Dabo (like

Django, it's too much of a moving target for someone to dabble with in

their spare time -- and unlike Django, it hasn't even the benefit of

rapidly out-dated paper books!)...

I'm curious about what you consider "deletes 2nd row". Your

statement "data was there before ... data is absent after" makes me

think you are defining a delete as "user blanked out all fields of the

record" -- technically that just means the user, well, nulled the field

contents but is not considered a deletion.

Most interfaces that I've seen with a record deletion capability

rely on either a column on the form with a check-box, to indicate that

row should be deleted (this format allows multiple deletions at a time

from a tabular/grid display), or an explicit action

(context-menu/right-click menu) ON EACH row, with a delete "command"

that takes effect immediately (well, maybe after a pop-up confirmation

"Are you sure you want to delete XYZ").

Hopefully the interface logic is smart enough to internally tag

records that have had changes performed on screen, and will issue

database updates when the screen is changed (on tabular/grid systems,

this could be whenever the user changes to a different row, only if the

"current" row had been modified; or it could cache all those modified

rows and submit them as a batch when the entire page is

exited/saved)[Reading ahead, this may be what is described in the

master's voice]

>Then I can call delete().

>Otherwise I call save()

>(along-with requery(), seek(), setFieldVal())

>Similarly, I have to trace-out newly added records.

>

>This becomes very complex.

>Definitely, dabo must be having a proper way to do this.

>

>I request this list to help me out.

>

>Thanks,

>

>Vineet

>

>

>--- StripMime Report -- processed MIME parts ---

>multipart/alternative

> text/plain (text body -- kept)

> text/html

>---

--

Wulfraed Dennis Lee Bieber AF6VN

wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/

_______________________________________________

Post Messages to: Dabo-users@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users

Searchable Archives: http://leafe.com/archives/search/dabo-users

This message: http://leafe.com/archives/byMID/hrp7j7db9pn3km3gpetpumpddok68j8u3u@4ax.com