StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2830250
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
24
CommunityOwnedDate
CreationDate
2010-05-13T20:55:54.497
FavoriteCount
0
LastActivityDate
2010-05-18T23:35:04.493
LastEditDate
2010-05-18T23:35:04.493
LastEditorUserId
30433
OwnerUserId
30433
ParentId
2829084
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I have a better understanding of your problem now - thanks for posting the updates to your code. I'm updating and elaborating on my answer to explain your problem and offer some solutions. I'm sure you know, but it won't hurt to preface this with a basic review of the general MVC pattern as it relates to URI structure. That is, in the example of <code>site.com/home/survey/new</code>, the first segment <code>home</code> is the controller class name, the second segment <code>survey</code> is the controller function name, and the third segment <code>new</code> (and any segments after this) is an ID or variable passed to <code>survey()</code>. <a href="http://codeigniter.com/user_guide/general/urls.html" rel="nofollow noreferrer">More here</a>. Your code isn't working because you never pass a variable to <code>survey()</code> via the URI when you submit the form, so "new" never exists in the URL, and therefore <code>$method</code> is always set to "update". So, <blockquote> "How can I pass $method to the _submit() function correctly?" </blockquote> There are a couple of options for doing this. Each one simply requires that you determine whether a user->survey relationship exists in order to set <code>$method</code>. You can then pass <code>$method</code> on to the appropriate functions. For my example below, I'm going to assume that a user can only have one survey. If that's not the case you'll just have to account for a unique survey ID associated with a unique user ID. One possible scenario goes like this (again, this assumes that a user can be associated with only one survey): <ol> <li>User submits survey</li> <li>Upon form submission, check to see if a survey already exists for that user</li> <li>If so, set <code>$method="update"</code> otherwise set <code>$method="create"</code></li> <li>Proceed to pass <code>$method</code> to the other necessary functions</li> </ol> An alternative solution might look like this: <ol> <li>In your controller function that calls the view file of your survey, determine if a record already exists for the user.</li> <li>Pass that data to your survey view</li> <li>In the view, modify the form action so that it passes that data (either "create" or "update") to the survey() function when the form is submitted.</li> <li>In <code>survey()</code>, set <code>$method</code> based on the data supplied</li> <li>Proceed to pass <code>$method</code> to the other necessary functions</li> </ol> I'll use the first option as an example and outline the logic you would need (forgive the somewhat pseudo-code, but you'll get the idea): survey() function: <pre><code>function survey() { // instead of determining whether "new" is part of the URI (which it never is), // check for an existing survey associated with the logged in user's ID $id = $this->session->userdata('id'); $query = $this->db->get_where('Survey', array('user_id' => $id)); // if the above query returns a result, set $method="update" // otherwise set $method="create" if ($query->num_rows() > 0) { $method="update"; } else { $method="create"; } // whatever other logic you need here // pass $method to survey_form() $this->survey_form_processing->survey_form($this->_container, $data, $method); } </code></pre> survey_form() function: <pre><code>function survey_form($container, $data, $method) { // your other code here if ( $this->CI->validation->run() === FALSE ) { // Output any errors $this->CI->validation->output_errors(); } else { // Submit form (w/ $method parameter - this comes from survey()) $this->_submit($method); } } </code></pre> _submit() function: <pre><code>function _submit($method) { // your other code here if ($method == "update") { // do something } elseif ($method == "create") { // do something else } } </code></pre> As a side note, there are probably better ways to structure what you're doing. For example, in my pseudo-code above, the database interactions should probably be happening in a model. For clarity, though, they are included in the controller. I hope that helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCodeigniter: Using URIs with forms
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USColin Brock
UserOwnerUserId
1. USColin Brock
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCodeigniter: Using URIs with forms
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.