> Anyways, why not set back to null when empty instead of zero? I seem
> to recall some code in the Bakery that automatically converts all
> empty strings to null for nullable fields. I'm taking a similar
> approach in my application.
Exactly, null means "not known".
> >
>
--~--~-~--~--
Phone number should be of type char and not integer. You'd never do
math on a phone number, right?
Anyways, why not set back to null when empty instead of zero? I seem
to recall some code in the Bakery that automatically converts all
empty strings to null for nullable fields. I'm taking a similar
typo? phone_buisness -> phone_business
On Fri, Jul 18, 2008 at 5:47 AM, RJ <[EMAIL PROTECTED]> wrote:
>
> got the solution
> before saving , i am making a check as follows:
>
> if($this->data[xyz][phone] == ' ')
> $this->data[xyz][phone] = 0;
>
> On Jul 18, 2:27 pm, schneimi <[EMAIL PROTE
if($this->User->save($this->data))
{
//success
}
here is an extremely well written article clear and well paced (few errors
minor easily correctable errors the validation array example is missing a
username => ..) - so read and digest (not just copy and paste)
http://www.jonnyreeves.co.uk/2008/0
got the solution
before saving , i am making a check as follows:
if($this->data[xyz][phone] == ' ')
$this->data[xyz][phone] = 0;
On Jul 18, 2:27 pm, schneimi <[EMAIL PROTECTED]> wrote:
> If there is no value set for this field, I guess it's trying to set an
> empty string as default. I
If there is no value set for this field, I guess it's trying to set an
empty string as default. I guess the only way is to care about the
field not beeing empty respective is set to 0.
But it looks like you are using an int-field for a phone-number, so I
suggest to simply change it to a (var)char
got the query by putting the DEBUG level to 2...
the error that i get is :
Warning (512): SQL Error: 1366: Incorrect integer value: '' for column
'phone_buisness' at row 1
the column phone_buisness is 'int' with default as null.
When i enter any valid number , the record is saved , but when i le
Still not able to figure out the error, i feel its with the query
thats formed when Model::save() is called.
Could any one tell me how to get the query string when Model::save()
is called.
On Jul 18, 12:03 pm, schneimi <[EMAIL PROTECTED]> wrote:
> Just set the debug level to 2 in the core.php:
>
Just set the debug level to 2 in the core.php:
Configure::write('debug', 2);
RJ schrieb:
> I am having problem in saving the records in the database.The code is
>
> if($this->User->create($this->data) && $this->User->save())
> {
> //success
> }
> else
> {
> //Failed
> }
>
> The control always
I am having problem in saving the records in the database.The code is
if($this->User->create($this->data) && $this->User->save())
{
//success
}
else
{
//Failed
}
The control always goes to else block .How can i track the problem.
Basically is there any way to get the SQL query string.
--~--~-
10 matches
Mail list logo
