On 01/09/2011, at 7:51 AM, Chris Lalancette wrote:
<snip>
One example of this is public_addresses; the
public_addresses field I get from the deltacloud backend looks correct
(
ec2-50-7-27-214.compute-1.amazonaws.com, or whatever), but when it is saved
into the database it looks odd (---\n- ec2-50-7-27-214.compute-1.amazonaws.com\n).
Since dbomatic is not doing this manipulation, I can only presume that some
observer is screwing it up, but I can't see how.
Any idea if this weirdness happens with all database backends? Maybe it's a
character set conversion problem or something?
For a PostgreSQL database backend, it should be possible to turn on full logging
of all SQL statements that hit the database. Slows things down, but useful to
see what the actual SQL doing the insert/update looks like. Might lead to
"aha!"
type of thing. ;)
The PostgreSQL "log_statement" setting in the postgresql.conf configuration
file
turns it on. Just set it to "log_statement = all".
Hopefully I'm talking about the correct "database" you're meaning here.
:)
Regards and best wishes,
Justin Clift
--
Aeolus Community Manager
http://www.aeolusproject.org