On Sun, Feb 15, 2009 at 6:59 AM, ara.t.howard <[email protected]> wrote: > well that is indeed true - but sometimes you absolutely need this > functionaliy. currently, with ar, you cannot even save a record to a > postgresql field which is both non-null and has no default value. ar > will try to insert 'NULL' into the column and blows up.
Could you explain this? It works just fine for me. You create a new model instance with that value set and it saves ok. Of course, you have to explicitly give the model that value for it to work in a non-null, defaultless field, but that's the whole point of making it non-null and defaultless in the schema. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
