many thanks to you guys. i do appreciate for all ur replies here. i
found it really useful to me. and yeah, i already decided that i could
continue using cakephp as my framework (thnks god). yeah, i'd been
searching many posts related to this issue and guess what, i didn't
see there are lots of
100 tables, ouch .. yeah sounds like your going to have to leave it as
it is, but as others are saying it should work with a little extra
configuration. Good luck and get back to us with how you find it.
@phpMagpie
On Sep 6, 2:10 am, Greg Skerman gsker...@gmail.com wrote:
I told you how to do
to be honest,i don't really want this happen.but what am i supposed to
do?i cant build new database since the current database have lots of
datas inside. after i read ur reply i started to think like that as
well.my work will be hard later. i have to define lots of things on
the model and i don't
Cruisine,
How many tables are we talking about? Is the old application using
this database still going to be accessing it or will your new one be
the sole point of access?
As Greg says, it certainly can be done, but soo much easier to write
an import script and migrate the system to a new
@WebbedIT
its up to 100 tables and still being accesed by that application...in
fact this application is still running..due to the integration issue
with another application which is using PHP as the engine, i need to
re-develop the application into PHP. and i considered to use Cakephp
as the
that is the limitation of the framework, i think. If mapping is too
difficult and it makes system hard to maintain in the future, maybe changing
to the other frameworks is a not-too-bad solution (Zend ??? )
On Mon, Sep 5, 2011 at 7:19 PM, Cruisine cruisin...@yahoo.co.id wrote:
@WebbedIT
its
@tran cao thai :
umm...yeah changing into another framework is the fastest
solution...but we're working as a teamwork..so to decide changing the
framework is not that easy since the entire team member are used to
have cakephp as their framework to build an application. so as long as
it's not too
I do not see any problem in what you describe above. I understand that it is
comfortable to use the naming conventions whenever you can, but that should
not stop you from using CakePHP with an existing database that does not care
about these conventions.
CakePHP follows conventions *over
I told you how to do it :) its not impossible, you just risk it becoming an
unmaintainable mess.
There are many tables I use which come from other systems/are static dumps
of tables out of systems i need to use as reference data but don't want to
muck up the table definitions etc - and I
hi guys, i need to know something important about naming convention.
yeah, i've been using naming convention while developing all my app
all the time. but recently a problem appeared. let say i've got a
project to re-developing an app ( from non-cakephp to cakephp) which
already had a database.
http://book.cakephp.org/view/1057/Model-Attributes is a good place to start.
you can configure in most circumstances cake to talk to any old database -
you just end up losing some of the magic and writing more code as a result.
for a model which does not comply with the convention you will at
11 matches
Mail list logo
