Posted by Angelos Devletoglou on 12/03/05 13:23

Hello,

A. Timurhan Cevik wrote:
> Like any database driven program you should start by defining your
> schema ?
> Thats not the way to oop. Never do that, if you plan to program oop.
> Sure, you should do it, but if you are procedural programming or you
> lack skills to construct an oo program.
>

Ok I see you know what you are talking about and I agree with you.
My problem you see is that At the moment I have a working application
but it is writen in a procedural way and ofcourse I short of have the
database ready... The good thing is that I don't want to migrate
anything from the old system so I start from scratch.

Now if describe you once more my case... would you be able to find me a
solution in the design and how can I simply interpret it in
programing... It is something that I have to have it before christmas
and that makes me nervous...

If you have some time read the case below again otherwise thanks a lot
for your help until now ;)

PHP4 I can't change that.
So here is the case again in parenthesis I will write how I interpret
them in programming:
A content(class) management system will be able to let registered
users(class) to add/edit/delete/publish/unpublish and
restore(content:methods) content.
When the content is added it will be unpublished. Then the user will
publish it. If the content is been edited it, the original version will
stay published but the new version will go be unpublished. Once the new
version is been published the original content gets backuped and the new
gets published.
We can have any type(content:attribute) of content, starting from
Pages,News,Events to Products and Photos.
*****************************************************************************
Now that was sort of my case. Can you tell me how would you design the
application and your database ?
And how you would interpret them in very very brief code(Keeping in mind
the PHP Ver4.X.X).

Thank you...

[Back to original message]