Hi,
my first reaction comes from a CocaCola commercial for "Fanta", going : No … No … Noooooooooooooooooooo :shock:
my second reaction : Why an SQL table, why not a custom content type, derived from sys.base. This way, you can use all the standard Alfresco APIs and are release safe for future versions.
my third reaction: If you reeeaaallllyyy need an SQl table, why does it have to be inside the Alfresco schema ? Why not use a separate database schema on the same DBMS as Alfresco and use the same connector to access the data. You still have one admin job, configuration management, desaster recovery, network infrastructure, only two databases, "alfresco" and "myAlfExtension".
Oh - if you really need to extend the Alfresco schema (which I rather doubt), you will have to rewrite part of Alfresco code - and merge each time, you try to integrate new Alfresco releases / fixes. A secure job for your software guys for as long as your application runs, so maybe you should redo your business math.
Bottom line is: "Why on earth do you need that" - well maybe starting from "what are you trying to achive in businessterms" is the better approach, but the first one does fit better with your question.
Norgan
