Is there any sensible way to convert as part of a migration these or is it pain and suffering only?

Roy Lambert

Roy,

<< Is there any sensible way to convert as part of a migration these or is
it pain and suffering only? >>

Just thinking out loud here: how would the EDB migrator know which BLOB
columns contain table streams ?  I guess we could add a parameter that would
name the BLOB columns.....I guess it's possible.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


><< Is there any sensible way to convert as part of a migration these or is
>it pain and suffering only? >>
>
>Just thinking out loud here: how would the EDB migrator know which BLOB
>columns contain table streams ? I guess we could add a parameter that would
>name the BLOB columns.....I guess it's possible.

Thinking about it walking the dog this morning I've decided I'm going to a database independent structured storage paradigm (ie probably XML) which will be a bit slower but very so often (eg V3 - V4 - ElevateDB) I'm faced with these conversion problems which always seem to give me grief.

Which raises a question - any projected date for XML support? Its not in the product roadmap.

Roy Lambert

Roy,

<< Which raises a question - any projected date for XML support? Its not in
the product roadmap. >>

The only XML support I have on the list right now is the import/export.  You
can write external functions that manipulate/query XML, if you need
something right away.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Not a problem to roll my own, its just that I remembered something about xml support so if you were doing it anyway I'd just nick your stuff.

Roy Lambert