- Introduction to POG
- Setting up PHP, MySQL etc.
- Designing your objects
- Generating your code
- Description of the generated code
- Edit configuration file
- The Setup Process
- Using the code: Save()
- Using the code: Get()
- Using the code: SaveNew()
- Using the code: GetList()
- Using the code: Delete()
- Using the code: DeleteList()
- Advanced: object relations
- Advanced: Set{Parent}()
- Advanced: Get{Parent}()
- Advanced: Add{Child}()
- Advanced: Get{Child}List()
- Advanced: Save(deep)
- Advanced: Delete(deep)
- Advanced: Add{Sibling}()
- Advanced: Set{Child}List()
- Advanced: Set{Sibling}List()
- Advanced: Get{Sibling}List()
- Advanced: DeleteList(deep)
- Customizing POG-generated code
- Customizing: Extending POG Objects
- Customizing: Plugins
- Examples
- Examples: User registration system
- Examples: User authentication
- Examples: Survey form
- Examples: Using POG with AJAX
- PDO: Introduction
- PDO: SQLite example
- PDO: Firebird example
- PDO: PostgreSQL example
- PDO: MySQL example
- PDO: ODBC example
- Troubleshooting
- Troubleshooting: Data appears encoded
- Troubleshooting: Can't regenerate object
- Troubleshooting: Can't seem to Save()
- Troubleshooting: Can't get object / object attributes from database
- Troubleshooting: Can't open zip file on Mac
- Troubleshooting: Setup screen is blank
- Videos
- Appendix: Creating table(s) manually
- Appendix: Regenerating objects
- Appendix: Generating objects using SOAP
- Case Study: Gravity GTD
- Case Study: Web Form Factory
Back to the Code Generator
The POG Weblog and RSS feed.
The POG Google group
Troubleshooting: Data appears encoded
When you take a look at the data saved in your database directly, you’ll notice that the information appears encoded. For example, you might see something like this:
objectid | var1 | var2 | var3 ------------------------------------------------------- 2 | 666 | dmFyMg== | dmFyMw==
and you were expecting something like this instead:
objectid | var1 | var2 | var3 ------------------------------------------------------- 2 | 666 | var2 | var3
This occurs because POG automatically encodes your data before it is stored in the database and decodes it when it’s retrieved. The encoding and decoding format used is Base 64. The data is encoded/decoded to protect your web application from SQL injection attacks. It also allows saves the end-user from having to explicitly escape the data. However, it does have its price: data encoded in base 64 takes 33% more space than unencoded data.
There are many online base 64 encoders/decoders that you can use to decode the data manually.
For more information on the Escape functions, take a look at this article from the POG weblog.


