[EMAIL PROTECTED] wrote: > Mini, > > That's a great suggestion. I'm also using sql views (not to be confused > with Cake views!) to make things easier in my project. > > Incidentally, I wonder if the use of Postgres could reduce the number > of steps in that solution by means of triggers. I suspect a calculated > field could be constructed transparently, including updates, in > Postgres. I've used postgres outside of cake and found it very pleasurable to use, particularly when it came to creating functions (I'm a pre mysql 5.x user). As for triggers, the cake steps might be reduced, but then the dbserver has to deal with the triggers. On mysql 5.x for example triggers occur on INSERT, UPDATE, and DELETE. I don't see where it can deal with calculated fields in this case (other than creating a field inside of the users table and call it full_name and have the trigger concatenate lastname and firstname each time on INSERTS and UPDATES).
> I looked into Postgres for myproject, and was pleased that the > translation from Mysql to Postgres was really quite easy, and worked > fine --- but Mysql seems to have better development tools available, at > least in my limited investigation. Not sure what you mean by tools, but there are plenty out there for both I suppose. > Regards, > > Ralph Thanks for the additional information. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
