I will concur with Richter here. It is far better maintenance-wise to
keep all your application logic in the app and not distribute that
around into the database. The only time a view is of use is when an
outside batch-script or cron job might use it as that is not directly
related to your appl
Thank you for your suggestion.
I will rethink my design.
Himanshu
From: Richtermeister
To: Symfony users
Sent: Sat, 26 February, 2011 10:57:44 PM
Subject: [symfony-users] Re: dynamically extending classes
Hi Himanshu,
this seems overly complicated. Since
Hi guys,
a question: is it possible to define a custom request header for an esi tag?
Seems like Oracle, in its own application server, has implemented the
esi:environment tag, which lets you define custom headers for ESI
requests:
http://download.oracle.com/docs/cd/B15897_01/caching.1012/b14046/
Thanks for that plug in link and the ideas.
2011/2/26 Grzegorz Śliwiński
> Michal's idea is one way, although personally wouldn't add that many
> fk's into Comment model. Each new model that will get commented, will
> result in modifying Comment table. If it'll grow up, ALTER TABLE might
> take
I don't think its a bug. It's maybe more along the lines of a feature that
would be nice to have.
Maybe try this
http://www.symfony-project.org/plugins/sfDoctrineFBAutocompletePlugin
On Sat, Feb 26, 2011 at 11:23, Javier Garcia wrote:
> Ok, now I understand how this widget works..When you creat
It was actually easy. I also wanted to create custom labels from inside the
Form Class. Lol
Thanks for tha' tip.
2011/2/26 Jan Eichhorn
> Hi,
> thanks for your help.
> Thats actually helps a lot.
>
> Greets Jan
>
> --
> If you want to report a vulnerability issue on symfony, please send it to
>
Hi Himanshu,
this seems overly complicated. Since you're getting the same fields
from the database regardless of which user is logged in, you should be
fine using the same class to access those fields. The model shouldn't
change depending on which user uses it, only different data should be
access
W dniu 26 lutego 2011 16:36 użytkownik Grzegorz Śliwiński
napisał:
> Michal's idea is one way, although personally wouldn't add that many
> fk's into Comment model. Each new model that will get commented, will
> result in modifying Comment table. If it'll grow up, ALTER TABLE might
> take long tim
The config has changed since PR6, so if you are using PR6, it would be
"app.config:" instead of "framework:".
On Feb 26, 10:13 am, Alexander Kachkaev
wrote:
> Thank you, Christophe. The idea is rather clear. Unfortunately, when I write
>
> framework:
> exception_controller: MyController\Controlle
Ok, now I understand how this widget works..When you create this kind
of widget, it actually creates two fields: autocomplete_my_field (the
field that is showed and where you insert the data (values of the
array elements) and my_field (a hidden field, where the keys are
inserted).
This widget work
Michal's idea is one way, although personally wouldn't add that many
fk's into Comment model. Each new model that will get commented, will
result in modifying Comment table. If it'll grow up, ALTER TABLE might
take long time.
Second idea is to create association tables for each commented model
(i'd
Hi,
thanks for your help.
Thats actually helps a lot.
Greets Jan
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group,
Hi, I want to extend base classes dynamically.
Following explains my requirements.
I have a table 'Property'.
Columns are 'property_id', 'owner_id', 'name' and many more.
So default there will be BaseProperty class, Property class extending
BaseProperty class.
I want to use mysql views.
views
13 matches
Mail list logo
