So the answer to the SQL server problem I mention below is to use a field of type ntext for the profile instead of binary.
Craig -----Original Message----- From: Craig Connell [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 4:39 PM To: 'Jetspeed Users List' Subject: RE: PSML and SQL Server (or Oracle) Reading my e-mail ... it should say: ... The endresult is the while the profile gets into the database, many of the XML strings end up unterminated as they will not fit into the column. .... Not ... The end result is the while the profile gets into the database, only XML strings end up unterminated as they will not fit into the column. ..... Craig -----Original Message----- From: Craig Connell [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 4:25 PM To: 'Jetspeed Users List' Subject: PSML and SQL Server (or Oracle) Recently I have looked to move the PMSL files from Jetspeed into a SQL Server database. It seemed straightforward enough (I've done it for HSQL) and the import ran OK. The problem is this .... The binary type that the profile (xml) is placed into is only capable of holding 8000 characters (the scripts actually set it up to 7192). The end result is the while the profile gets into the database, only XML strings end up unterminated as they will not fit into the column. I have some PSML / Profile information that is around 8500 characters, and could get larger. There are some tricks with regards to SQL Server for putting information of this size into the table (writetext will let you do this), but would Jetspeed work with this data if I did manage to get it into the database? Anybody tried this or had any issues in this area? Any recommendations? I have tried this with Oracle as well and believe that I am going to run into the same problem (although I have not gotten that far since I have multiple schemas associated with the SID, so I can't get the import to run properly - any ideas on that would be great too!). Thanks for any help. Craig --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
