Leon,
I just checked out all required plugins to generate a grid.
Using your old sfGridExtjs3plugin, i get inheritance errors.
it seems the sfGrid class variables cannot be reached by any subclass
(private).
When I change them to 'protected' the subclasses are allowed access
and all works fine.
@david I am also interested in your solution.
My 2 cents:
At the moment we are working with views by letting Doctrine create
tables from the VIEW model classes, and the overwriting them with an
SQL to create the actual views.
I have managed to keep the relations (FK) out of the the DB by
am, E_lexy alexk...@gmail.com wrote:
@david I am also interested in your solution.
My 2 cents:
At the moment we are working with views by letting Doctrine create
tables from the VIEW model classes, and the overwriting them with an
SQL to create the actual views.
I have managed to keep
Hi Adrien,
We are in the process of changing a large project to Doctrine, because
we found the DQL language better suited for our complex queries.
Having done Propel for 1,5 year, Doctrine is easy to learn and much
closer to (old skool) SQL.
Also Doctrine is a bit more flexibel. There is
@ floria: you're right, but there problem is no less ;-)
I have tried doctrine, but the problem remains the same.
When you have a non-hydratable field in your query, you cannot use
sfDatasourcePropel/Doctrine, because the results gets hydrated toward
a model.
So I tried the sfDatasourceArray
... note the case of that i
after the get. Perhaps in your code you are calling the method with bad case
On Mon, Sep 7, 2009 at 11:34 AM, E_lexy alexk...@gmail.com wrote:
I am trying to use sfGrid based on a custom query-datasource.
This custom query contains a result of a calculated field
I am trying to use sfGrid based on a custom query-datasource.
This custom query contains a result of a calculated field.
Symfony complains a bout not being able to find a setter. -
understandable.
I believe i need make a setter, but where? in Idea?
Datasource:
[code]
Indeed Symfony permits i, but I have had trouble getting fixtures to
load on tables with foreign keys to itself.
It comes down to a chicken and egg situation.
For instance:
user:
id: ~
created_by_user_id: { type: integer, required: true, foreignTable:
user, foreignReference: id }
will work
