42 <column>
43 <name>xcap</name>
44 <type>text</type>
45 <type db="postgres">bytea</type><!-- Bug 1684821 -->
46 <description>xcap</description>
47 </column>
I think this is wrong. text should be fine. The problem is in the
presentity table (body column).
presnece module stores body as DB_BLOB - thus bytea escaping is
performed. But when postgresql uses "text" for body column, the result
column is DB_STRING and unescaping is not performed. Thus,
presentity.body must be type bytea in postgresql.
Thus, to have consistent DB schemes why not use BLOB in mysql and bytea
in postgresql?
We could also change the XML definition not to use SQL data types but
openser data types, e.g.:
70 <column>
71 <name>body</name>
72 <type>DB_BLOB</type>
73 </column>
Then when generation the SQL files, the DB_BLOB is generated to the
corresponding database data type.
regards
klaus
Henning Westerholt wrote:
Revision: 2310
http://openser.svn.sourceforge.net/openser/?rev=2310&view=rev
Author: henningw
Date: 2007-05-29 02:02:31 -0700 (Tue, 29 May 2007)
Log Message:
-----------
use bytea instead of text for postgres xcap_xml table, bug 1684821
Modified Paths:
--------------
trunk/db/schema/pr_xcap_xml.xml
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
