StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13193570
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-02T10:37:32.287
FavoriteCount
0
LastActivityDate
2012-11-02T10:37:32.287
LastEditDate
LastEditorUserId
0
OwnerUserId
626692
ParentId
13193063
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I have no idea if this does what you want it to or not, but I think you could benefit from reading the book "Code Complete" by Steve McConnell. Anyone who has to understand this code has to work very, very hard to understand the intent, and the deeply nested logic statements make it hard to see what's going on. Firstly, as @yes123 says, indentation helps. Secondly, comments would be nice. Thirdly, reducing the complexity would really help. For instance, instead of <pre><code>if ( isset( $_POST['code_search_submitted'])) { </code></pre> You might say: if (isValidSearch($_POST)) { <pre><code> } if ( isCodeSearch($_POST)) { </code></pre> and wrap your check for the post var into a separate function. Next, you might wrap the inner body of your IF statements into functions too - for instance, replace if (is_numeric( $_POST['searchText']) && (strlen($_POST['searchText']) == 4)) { <pre><code> $searchCode = $_POST['searchCode']; if ( $searchCode == 1 ) { $_SESSION['searchCode'] = 'TutorCode'; } elseif ( $searchCode == 2 ) { $_SESSION['searchCode'] = 'InstituteCode'; } $_SESSION['searchText'] = $_POST['searchText']; } </code></pre> with <pre><code>if (isValidSearch($_POST)) { handleSearch($POST) } </code></pre> Next, I'd encourage you to split the business logic in your app from the display logic - wrapping HTML statements inside your business logic (e.g. the Javascript errors) makes it REALLY hard to maintain. Consider an MVC framework. This also applies to separating out the business logic from the application logic (the output buffering for instance) - for a non-trivial application, you want to be able to modify the business logic without worrying about breaking the application logic and vice versa. Your sample code suggests that a simple change in the business logic (e.g. adding a new type of search) could easily lead to someone forgetting to re-set the output buffer...
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCreating A Logic In Best Way
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USNeville Kuyt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.