Re: [PHP-DB] Saving state

2003-09-16 Thread Luke Skywalker
Sounds fairly complicated, but wat about storing the information in session
variables? and using multi dimensional arrays to store the information

eg

Array
(
[call_1] = Array
(
[name] = john smith
[number] = 555-555-555
[time] = 2003-10-17 10:41:00
)

[call_2] = Array
(
[name] = bill johns
[number] = 555-555-555
[time] = 2003-10-16 07:41:00
)

)


but it really depends on how you want to do it, it might be beneficial to re
query the database every time, especially if its going to be multi-user,
because what happens if 1 person logs a call, how will the other person
using the system know that a new call has been logged, re-querying it
shouldnt take too long, and would provide advantages when there is more than
one user, and you would have no synchronisation problems

Luke

- Original Message - 
From: Shiloh Madsen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 17, 2003 10:24 AM
Subject: [PHP-DB] Saving state


Sorry about the cross posting, as im not exactly sure what would be the best
method to handle this, but im trying to set up a web application with a
tabbed interface. Each tab will have a form to enter data, and the requisite
save and continue button. Heres where things get hard though. I want to be
able to allow users to click on a previous tab to refrence, change, update,
etc the information on those tabs. How do i save the state of these tabs so
that they can be reaccessed? Just so you have a little more information, im
trying to make a kinda simple call logging system with a customer tab which
would hold customer info and a calls tab which would store call info and
allow you to switch between call records. all of this data would be stored
in a database, but i dont want to actually have to send a new query to the
database just because the user clicked on a previous tab...if this would be
possible. Also, if anyone has an idea as to how i can implement this a bit
more intelligently, im open to suggestions, but the tabbed interface seemed
to be the most user friendly. And yes, the web interface is important, which
is why im not trying to do it in c++ or something like that.

Shiloh

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DB] Saving state

2003-09-16 Thread Luke Skywalker
Yeah, that is a good way to do it, i would do something similar too but
Shiloh
seemed to not want to requery the database, althought querys in this case
would
be the quickest and simplest way to get the historical information, which
would be
stored in the database already, and as you said, update querys if you want
to change
the information loaded into the form. If you need to avoid the database, the
only
other way i can see of keeping the information is adding it to variables at
the same
time as you add it into the database, and when you need to re-access the
info, pull
it from the variable instead of the database, but that could get messy

Luke

- Original Message - 
From: Duane Lakoduk [EMAIL PROTECTED]
To: 'Luke Skywalker' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, September 17, 2003 12:39 PM
Subject: RE: [PHP-DB] Saving state


 Luke, Good point, this list is set up different in that Reply ONLY
replies
 to the individual poster, not the list.  Have to use reply to all.

 I have added the list address to this post. To all concerned,  this thread
 contains some off list conversation that may be of interest,
particularly
 to the original poster.

 Luke, I agree, both methods will probably work well, as you said,
'depending
 on the situation'.
 To expand on the issue of retrieving previously posted data into a
 multi-tabbed form.  In this case, I would normally show the user a list of
 previous posts or perform a search.  Selecting a previous post would load
 the form with the historical data to allow reviewing one tab at a time.
 Just like loading any normal edit/view form, but with the tabs breaking up
 the form into individual parts of the same record.  Edits and updates
are
 performed and posted using a similar process to the original post but
using
 an UPDATE WHERE instead of an INSERT INTO statement.

 List, Sorry if this post is ugly.  Delete as necessary.


-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php