uncoupling object classes from SQL

[Anon]

I'm curious as to how folks code their object classes to easily save/get object data from the db. I would like to somehow separate my sql form the class so I could easily make changes to my db structure without mucking with my classes, if that makes sense. I just hate hard-coding my sql statements in my classes, especially if I want to share the code with someone. I don't want to force them to build their db like I do.

Any ideas, I would appreciate any methods that you might offer.
brian

[Anon]

You could try using a database wrapper, like PHPLib. This would allow you to use a generic API for all your database calls in your classes without dependency on any particular database.

Obviously if your classes rely on your database structure, anyone that uses your code will have to set up there database accordingly to use them.

--Vamsi
http://php.vamsi.net

[Anon]

You are correct, others would have to model their db like mine. Do most people simple include the necessary sql inside their object methods?

Brian