Use POST when you don't want users see or change parameters and alert user on resent form.You can use POST with a redirection result, it will prevent retransmissions definitely.The first thing to do is check your Postgre SQL installation for the existence of a database named test.All the examples in this chapter refer to this test database; if this database already exists, you might want to create a database with a different name.The form will obviously use post to send the changes to the server, but is post also most suitable for passing the id to the edit form? I'm not wanting a user to update a record without realising though - I'm referring to the passing of an id to to a form which would then allow a user to update the record of the id which was passed to it.If you don't want random people changing random values (changing the value in the url) you should use post.Please refer to the Postgre SQL Web site ( for installation and configuration documentation.This section describes the initial creation of the test database that will be used in the remainder of the examples in this chapter.
Examples of this configuration are detailed in Chapter 1, "Basic PHP." The standard Postgre SQL installation uses port 5432 to listen for TCP/IP connections.In some cases only one or two lines of code is necessary to perform a database action.(Page 1 of 4 )Regardless of its remarkable features, including its outstanding online documentation, a flat learning curve and a strict application of the Model-View-Controller pattern, the Code Igniter PHP framework still lacks an important characteristic that other competitors have already implemented in the form of native libraries.You will see how to make this connection using PHP later in this chapter.Initial installation and configuration of the Postgre SQL package is beyond the scope of this chapter.
To check for the existence of a test database, use the following command: Now that the database is created, you must create a user that will have access to the database.