Great diagnosis! Turns out somewhere in the code newlines were being
converted to '\n' (two characters) in order to prepare the data for
mysqlimport.
Sorry about the noise on the list for such a silly error.. placeholders do
in fact work exactly as expected, but not when combined with faulty code
Hi,
Please make sure that you are indeed trying to put a newline into
the database. The string, '\n', is a 2-character string.
The string, "\n", is a 1-character string (a newline).
So if your text variable is something like 'hello\nworld',
it's no wonder the DBI interface tries to preserve the
On Sat, Sep 01, 2001 at 02:38:05PM -0500, Mike808 wrote:
> ryc wrote:
> > ... I am having a problem with DBI (or the db) escaping '\n'
> > characters so when they are inserted into the database they become '\\n'
> > (ie a '\' followed by 'n').
>
> > Does anyone have advice on how this could be do
ryc wrote:
> ... I am having a problem with DBI (or the db) escaping '\n'
> characters so when they are inserted into the database they become '\\n'
> (ie a '\' followed by 'n').
> Does anyone have advice on how this could be done while still using
> placeholders so I dont need to prepare the que
I have a query that executes many many times that I would like to optimize
using placeholders. One of the fields that it will insert into is a 'text'
field and I am having a problem with DBI (or the db) escaping '\n'
characters so when they are inserted into the database they become '\\n' (ie
a '\
