Custom Applications and Multiple Database Tables

Hi,

I have been looking at modx for a while and was wondering whether or not to use Modx or a framework like cogeigniter symphony etc... for the website i am creating.
The website will have to have a custom back end with around 6 or 7 database tables in addition to what is provided by modx.
I am looking at modx because it has some things already done (user management,forum,posts,login) etc....

How hard is it to integrate a custom database solution into modx?
I have been looking for some form of tutorial and can only find where they implement one table with no relationships to other tables.
Is it possible to cleanly implement a custom back end with multiple tables? If so are there any tutorials available that implement multiple tables?

As far as my understand goes...
If i use a framework it requires more custom built functionality (own user table groups etc...) but I can implement it cleanly in the Mysql Database Designer, and use an MVC framework where i only need the code that is required.

If i were to use Modx I would have to import all of my custom tables into the modx database, create schemas for them, tie them to xpdo objects, then use them in modx.
How would the relationships be defined in the schema to make sure they are correct?

Unfortunately I am leaning towards using a framework because i can’t find many concrete examples and resources of how to implement multiple custom tables cleanly into modx.
I would like to use Modx though and was posting here hoping to find an example/resources/tutorials of this being done. I have looked at the single table implementation tutorials but it doesn’t help much for how to define relationships etc...

Any help would be appreciated.

Check out the following Extras, as they all use multiple tables and relationships:

- Quip
- Discuss
- Gallery

what is the advantage of using modx over a framework?

Quote from: atarax at Oct 28, 2010, 08:34 AM

what is the advantage of using modx over a framework?

The purpose of a Content Management Framework like MODx, IMO, is to allow those who aren’t PHP developers to contribute to the process in a logical way, and one that is tailored to their role in the process. Designers provide CSS and markup where needed, PHP developers provide the dynamic content and/or web application code, and other stakeholders can take the deployed site and easily edit the content they need to without worrying about messing up the design the designers provided or the code the developers contributed.

If it’s all you as a single person doing a project, and you are doing all the design work and development work, and maintaining the content, then why not just use a pure PHP framework (or even just plain PHP pages)? Well, if you are a fanatic about separation of content and logic like me, you might still choose to use MODx, but I’m a little crazy according to those that know me.
:o

thanks Jason that really cleared things up for me.

I am doing everything myself so im probably going to use a pure php MVC framework so i still have some seperation of content from the code

If my site ever becomes big enough where there are many people working on it at once I will switch over to modx.

Thanks for the help.

One advantage of MODx Revolution is the built-in convenience and power of xPDO.

See here: http://bobsguides.com/custom-db-tables.html

And here: http://bobsguides.com/revolution-objects.html

Another advantage is that MODx Revolution is really both a framework and a CMS combined. The real question is, do you need a CMS, and if so, why wouldn’t you pick one with a great framework built-in.