Hello Tumpa SINGHA RAY Magnolia is using JCR to store most if not all of the data - this is especially true for website content. Typically JCR is not restricting what data store is used "under the hood" to persist the JCR data - its persistence layer can and often is a RDBMS (especially in productive environments). However, from the Magnolia perspective, the data is stored in JCR nodes and properties - independent from the persistence layer.
Doesn't make sense to operate directly on the DB layer in the context of Magnolia website content (imho). Why would you do that? What is your use case? What is your goal? However - there is always a lot of space to customize Magnolia :-) Resources: - https://en.wikipedia.org/wiki/Content_repository_API_for_Java - https://documentation.magnolia-cms.com/display/DOCS/JCR+API - https://documentation.magnolia-cms.com/display/DOCS/Content+app+with+non-JCR+content I hope this helps, kind regards, Christoph -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=e8d23766-e688-4874-9d8a-5bf1613a4ab4 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
