StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6116220
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-24T20:07:52.027
FavoriteCount
0
LastActivityDate
2011-05-24T20:07:52.027
LastEditDate
LastEditorUserId
0
OwnerUserId
768392
ParentId
5958202
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
@dave I've been using CI for a while now, and generally speaking using its built in form support or doing it home brew is really no different. Personally I tend to lean towards home brew handwritten forms in a matter of speaking. Avoiding CI's form support all together. Although CI does offer "ease" of use so to speak for more novice users (and the gurus alike). I've always felt the same as you, its got a kind of restrictive feeling to it, top it all off when your making forms for CI using there system for it your basically doing the same thing as you would with standard HTML but also implementing in CI's syntax so it can handle it better. For me I do a lot of AJAX related stuff so the standard support doesn't help me much and usually gets in the way. I've worked on a few Professional level teams as well which have used CI as the backend framework but also share the same distaste for the form support CI has. More times then less its gotten in the way of development on both the front and back end then it has done any good. More times then less we would always end up going the route of standard HTML forms and just work with the standard PHP means of getting the posted data and then home brewing our own filters on an element to element need so we know we are getting what data we want to get without having to come up with some means of getting around any restrictions otherwise. So the short version to your answer is just go with standard html/php form handling. You will find a lot more support out there how to handle your inputs stand alone that way opposed to CI (matter of opinion). Also handling your forms this way doesn't muck up the works you can still easily work within CI with its other lib's and mod's I know this isn't a direct answer to your question but I felt I should at least put my 2 cents in. CI is a nice framework all around but its built on PHP so if you can do it with PHP you can do it within CI, and in the event of form handling I go the route of PHP rather than work with CI
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFastest way to build form - PHP/jQuery/CodeIgniter
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USchris
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.