Previously on the blog
RSS feed
  1. Using POG with Flex
  2. Optimizing your web application
  3. Regenerating large objects
  4. PHP4 or PHP5
  5. New and Improved
  6. Evolution of a cube
  7. POG Museum
  8. POG 3.0 alpha
  9. Initial Performance results Part 2
  10. Initial performance results
  11. Proposal: POG 3.0 object model
  12. Suggest a feature
  13. A new year, A new POG release
  14. Many-Many relations
  15. POG 2.5 Released
  16. POG 2.5 beta
  17. Automatic table alignment
  18. New version: 2.1.2 released
  19. RSS should work well now
  20. RSS feed glitches
  21. What's new in 2.1.0
  22. PHP Objects 2.1.0 (preview)
  23. PHP Object relations FAQ
  24. PHP Object Relations
  25. Searching base64 encoded text
  26. How to debug POG-generated objects
  27. POG UI Tips
  28. Featuring Of Interest links
  29. PHP CRUD
  30. POG 2.0.1: A better code generator
  31. A look at the POG SOAP API
  32. POG 2.0.0 released
  33. Coming soon: Generate parent-child objects
  34. Generated abstraction v/s dynamic abstraction
  35. Zend Framework preview
  36. Coming soon: Generate Objects through SOAP
  37. Easily save images and files to a database
  38. PHP, Paypal & POG
  39. Five advanced Code Generator tips
  40. PHP Pagination using generated objects
  41. PHP Code Generator benchmarks
  42. Representing database objects using an AJAX Tree interface
  43. Using SETUP in a production environment
  44. Description of the generated object package
  45. Introducing PHP Object Generator version 1.6
  46. Using AJAX and PHP Object Generator
  47. When to use Object->SaveNew()
  48. Generating PHP objects in 2006
  49. Happy Holidays
  50. A short video of the POG Setup process
  51. A sneak peek at POG 1.6
  52. POG Tip: Field limits
  53. Previous versions.
  54. Searching the blog and tutorials sections
  55. Generating code with "Other" SQL data types
  56. Five general POG tips
  57. POG source code locations
  58. Microsoft SQL 2005 Express Edition
  59. Impatiently awaiting PHP 5.1 and PDO
  60. Php Object Generator goes open source
  61. POG generates PDO compatible code
  62. Oracle to offer free database
  63. POG Google group
  64. Database Wrappers and POG
  65. Revisions
  66. The generator blog
  67. An explanation of the 'Escape' function.
  68. Mirror, mirror
  69. Using POG to solve real world problems
  70. A php object-relational database tool
  71. A simple and flexible Object Oriented approach to PHP


Want more Php Object Generator?
Back to the Code Generator
The POG Google group
The POG tutorials/code samples
The POG mirror site




When to use Object->SaveNew()

written 4127 days ago

While designing Php Object Generator, we wanted the Save() function to be ‘smart enough’ to know when to UPDATE a database record and when to do an INSERT. POG uses the objectId attribute to make this decision. The objectId attribute is an auto-increment field, which is automatically generated for all objects. The objectId is also by default, the primary key of the object. For more information, check out the Save CRUD method section of the tutorials. If the objectId is empty, POG will save the object to the database and assign the objectId after the INSERT. Upon subsequent calls to the Save() CRUD method of the same object, POG will UPDATE the corresponding row of the database. Therefore, using Save() does the job in almost all scenarios. Why then do we need the SaveNew() CRUD method?

There are specific situations where you want to force a database INSERT and this is when SaveNew() comes in handy. There are 2 main situations I can think of: The first one is when you want to clone an object within the database. In other words, you simply want to duplicate a row of your the database. The second is security. SaveNew() guards against unintentionally updating a database record with corrupt data. A rare and specific way this could happen is if, for example, you’ve created a user registration form whose input field names match the attribute names of your object, and in your code, you’re looping through the $_POST array and matching the input fields to attributes of your object as follows:

$keys = array_keys($_POST);
foreach ($keys as $key)
{
$user->{$key} = (isset($_POST[$key]) ? $_POST[$key] : ‘’);
}
$user->Save();

Someone could potentially create their own web form containing an input field called “userId” and perform a cross-domain POST to your script. The code above would grab the objectId value and assign it to the object. Upon Save(), POG will overwrite an existing record. This specific scenario can be avoided by using SaveNew() as follows:

$keys = array_keys($_POST);
foreach ($keys as $key)
{
$user->{$key} = (isset($_POST[$key]) ? $_POST[$key] : ‘’);
}
$user->SaveNew();

In the case of a user registration system or whenever the application logic dictates that only an INSERT (no UPDATE) should be performed, SaveNew() is the safer choice.


  Textile Help
About Php Object Generator
This is a weblog about the Php Object Generator (POG) project, OO PHP, databases and Php code generators in general.

Php Object Generator, (POG) is an open source PHP code generator which automatically generates clean & tested Object Oriented code for your PHP4/PHP5 application.

Subscribe to our RSS feed

Feedback, Feature Requests, Bugs to:
The POG Google group

Send us a Hello through email