Evaluating Tamino

, ,
1

Hi,
I am tasked to evaluate Tamino and had some technical questions about it. If someone can help with these, it is very appreciated.

  1. Does Tamino require XML schemas to be loaded? Or can it store ad hoc XML documents in a collection?
  2. Does Tamino support the notion of collections?
  3. Does Tamino support ALL of XML Schema, including xsd:redefine?
  4. Does Tamino allow for concurrent access to the database (i.e. someone can query the database while another thread is writing to it).

Thank you! I need to complete my eval by this week, so hopefully I will find these out by then.

Best Regards.

2

Hi

ad 1) Yes - but querying a huge number of documents that have no schema - and therefore no index may take some time !
And fast queries and huge number of docs are usually the reason for having a DB in the first place;-)

ad)2 Yes - in fact you always group doctypes using collections.

ad 3) Almost all features, but not redefine :frowning:
See the documentation at http://techcommunity.softwareag.com/ecosystem/documentation/Crossvision/ins441/tslref/nsxmlschema.htm

ad 4) The database Yes, the document beng updated - depends.
There are different kinds of locking (isolation levels etc etc)
See doc at http://techcommunity.softwareag.com/ecosystem/documentation/Crossvision/ins441/transact/tg-iso-level.htm

Finn

3

Great, thanks. A couple more questions for our evaluation. I appreciate the input. I wasn’t able to evaluate Tamino myself because it does not install on Windows Vista.

  • Does tamino support Xquery 1.0, XPath 1.0?
  • Does it support the notion of nested collections? Or just databases?
  • Does it support clustering?
  • How is the performance when more than 1 million documents are loaded into a database?
  • Does it provide user-level access control permissions? XACML?
  • Does it support XUpdate?

Thank you very much!
Darren

4

As far as I am aware of XQuery is supported fully, never found a strange behaviour lately but with some restrictions of the position() function in paths. XPath is supported as well but for some restrictions: I never found the sibling axis but I have a workaround now (see separate posting). Can’t say much about the other questions; there is an update language comming with Tamino, I think it is XUpdate, need to check the specs for differences.

BTW you can have more than one Doctype in a collection, i.e. different schemas, XSchema is supported, as far as I know, would have to check the specs again if there are deviations.

User-level access control: I talked to other people who wanted to have some sort of permission system for every node. Is this what you mean by XACML? I don’t have these security issues in my data.

Performance: I never created real benchmarks, my collections are too small to count as challenges, but some of my queries are really challenging :slight_smile: And the perfomance is subjectively quite impressive – in comparison to XQuery tools operating on the file system.

Hope that this experience report helps. Have fun with Tamino.