Re: Issue, not sure how to solve

On Tue, 2011-08-16 at 15:45 -0400, Dirk H Bartley wrote:
> Ok,  .. ..   I am feeling dumb.  I was figuring it was non-printable
> characters, but did not see any in the single line string.  Even now,
> when I search for 0E, vi is telling me that searching for 0E yields no

Can you search for \0E or \00 or \000?  Since it is non-printable you
have to search for it by the octal or hex value.

> results.  So how do I find the offending customer record this time??
> Then, How do I prevent such offending characters in from being put in in
> php in the future.

It is a nuiscance, and not just in this case but in web applications in
general (although if you never produce anything 'verifiable' such as XML
you may never notice - just odds things will occur occasionally).

Somewhere around here I've got a spell for fixing this kind of gunk; but
I can't seem to lay hands on it at the moment.

On a one-off basis I usually just go into DbVisualizer and fix them via
edit-cell.

> I assume I need to do some direct posgresql querries for searching for
> records with nonprintable charachters.  My guess is that if there is one
> there are more.
> Ahhhhh, the joys of users doing unexpected things.
> Thank you so kindly for your assistance.


-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc