Php Object Generator Tutorials
  1. Introduction to POG
  2. Setting up PHP, MySQL etc.
  3. Designing your objects
  4. Generating your code
  5. Description of the generated code
  6. Edit configuration file
  7. The Setup Process
  8. Using the code: Save()
  9. Using the code: Get()
  10. Using the code: SaveNew()
  11. Using the code: GetList()
  12. Using the code: Delete()
  13. Using the code: DeleteList()
  14. Advanced: object relations
  15. Advanced: Set{Parent}()
  16. Advanced: Get{Parent}()
  17. Advanced: Add{Child}()
  18. Advanced: Get{Child}List()
  19. Advanced: Save(deep)
  20. Advanced: Delete(deep)
  21. Advanced: Add{Sibling}()
  22. Advanced: Set{Child}List()
  23. Advanced: Set{Sibling}List()
  24. Advanced: Get{Sibling}List()
  25. Advanced: DeleteList(deep)
  26. Customizing POG-generated code
  27. Customizing: Extending POG Objects
  28. Customizing: Plugins
  29. Examples
  30. Examples: User registration system
  31. Examples: User authentication
  32. Examples: Survey form
  33. Examples: Using POG with AJAX
  34. PDO: Introduction
  35. PDO: SQLite example
  36. PDO: Firebird example
  37. PDO: PostgreSQL example
  38. PDO: MySQL example
  39. PDO: ODBC example
  40. Troubleshooting
  41. Troubleshooting: Data appears encoded
  42. Troubleshooting: Can't regenerate object
  43. Troubleshooting: Can't seem to Save()
  44. Troubleshooting: Can't get object / object attributes from database
  45. Troubleshooting: Can't open zip file on Mac
  46. Troubleshooting: Setup screen is blank
  47. Videos
  48. Appendix: Creating table(s) manually
  49. Appendix: Regenerating objects
  50. Appendix: Generating objects using SOAP
  51. Case Study: Gravity GTD
  52. Case Study: Web Form Factory


Want more Php Object Generator?
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.





POG documentation summary: