[In the Works] Datamapper ORM Class

[eluser]Michael Wales[/eluser]
We also created a new user from our signup form. That form looks like:

Code:

<form method="post" action="signup" name="signup" id="signup"><!-- Note: This doesn't matter -->
<p>Username:<br />
&lt;input type="text" name="signup[username]" id="signup_username" maxlength="20" /&gt;&lt;/p>
<p>Password:<br />
&lt;input type="password" name="signup[password]" id="signup_password" maxlength="20" /&gt;&lt;/p>
<p>Email Address:<br />
&lt;input type="email" name="signup[email]" id="signup_email" maxlength="120" /&gt;&lt;/p>
<p>&lt;input type="submit" name="signup[submit]" value="Signup" /&gt;&lt;/p>
&lt;/form&gt;

The magic happens because of how we named all of our input fields (not id - just the name parameter). We can now use the fromForm() method to easily pull all these values down into our model, validate them against our rules, and save them to the database. Remember how we didn't add any validation rules for fields like salt? That means no matter if a user changes your form to add in a salt field - it's not going anywhere near your database. All, without any real work on your behalf.

Finally we updated a user's information. You'll be glad to know that Datamapper doesn't just issue a wide-open UPDATE statement to the database - that would be to simple. Datamapper is optimized to the gills and will only issue updates for fields that actually change.