but in the situation I showed in my last example, it produces invalid
SQL. Shouldn't this be avoided, no matter what the value of the
variable?

Metastorage knew the variable had no valid value (hence it displaying
the "?" in the "PrepareQuery" line of the debug output), shouldn't it
be doing something with that invalid value? (Eg, set it to NULL in
SQL, or report an error and don't run any SQL)


On 19/09/2008, at 5:47 PM, Manuel Lemos wrote:

> Hello,
>
> on 09/19/2008 04:25 AM Nik Sands said the following:
> > Is metastorage NOT supposed to replace this with a NULL in the SQL
> in
> > this case?
> >
> > Is metastorage SUPPOSED to produce invalid SQL in this instance?
> > Shouldn't it instead be either substituting a NULL in the SQL? Or
> > otherwise producing an error in the 'persist' routine before
> trying to
> > run invalid SQL?
>
> I am not sure what you mean. The code generate by Metastorage sets the
> field to NULL if you set the respective optional variable to null or
> just not assign any value to it.
>
> --
>
> Regards,
> Manuel Lemos
>
> Find and post PHP jobs
> http://www.phpclasses.org/jobs/
>
> PHP Classes - Free ready to use OOP components written in PHP
> http://www.phpclasses.org/
>
>



========================================================
NIXANZ - http://nixanz.com/

Like to help out as a beta tester? Let me know which application
you'd like to test.





[Non-text portions of this message have been removed]