Hi,
That's not, what Richard wrote me ::( but when I insert text into table, is
this all OK?
name='John Smith"
name='John "the Big" Smith' //double quotes around `the big`
name='John ''the Big'' Smith" //two singe quotes around `the big`
....
so it's exactly the oposite way Richard wrote me....
Brona
> You can solve all your problems by using strictly standard
> quoting. The single quote (') is the quote character for
> strings. The double quote (") is the quote character for
> identifiers, which include column names. You don't need
> to quote an identifier unless it has white space in it, so
> you probably never need to use double quotes.
>
> >> I'm using email="[EMAIL PROTECTED]", it works
> Don't do that. Use single quotes for strings.
>
> >> email="email" causes to leave the field as it is
> Yes, that's exactly equivalent to email=email. SQLite
> recognized email as a column name, so it treated "email"
> as a quoted identifier (called a delimited identifier in
> the SQL standard). If SQLite had not recognized email as
> an identifier, it would have treated it as a string. If
> you use double quotes, you will get different behaviors
> depending on what is between the double quotes. If you
> use single quotes on strings and no quotes on identifiers,
> you will eliminate the confusion.
>
> Regards
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
