** This issue is now resolved ***
DISCLAIMER
I don't want this to seem like a giant bitch-fest over
sfDoctrineGuard, it works great thank you for writing it, REALLY. But
boy there were some frustrationg moments for me. I would hate to have
built a custom authentication class(es?) myself, so I t
> The db engines are within a few sub-versions apart (mysql 5.0.75
> server vs. 5.0.67 local)
Further info from:
http://dev.mysql.com/doc/refman/5.0/en/identifiers.html
"As of MySQL 5.0.52, aliases for column names in CREATE VIEW
statements are checked against the maximum column length of 64
ch
On Jan 11, 4:25 pm, Georg Gell wrote:
> This is a mysql specific error, because mysql only allows 64 bytes
> length (http://dev.mysql.com/doc/refman/5.0/en/identifiers.html). It
> seems that the SQL standard defines 128 bytes
> (http://bugs.mysql.com/bug.php?id=13942)
> I think you should file
This is a mysql specific error, because mysql only allows 64 bytes
length (http://dev.mysql.com/doc/refman/5.0/en/identifiers.html). It
seems that the SQL standard defines 128 bytes (
http://bugs.mysql.com/bug.php?id=13942)
I think you should file a bug report for doctrine.
Am 12.01.2010 00:31, sc
On Jan 11, 6:23 am, Gabo wrote:
> try to delete all tables and next symfony:doctrine
>
> Gabo
>
I rebuild completely, so that's ot it. Thanks.
--
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-
Thanks for the response!
On Jan 10, 11:58 pm, Frank Stelzer wrote:
> Hi,
> Looks like a SQL Problem. You should get a detailed explained error,
> when you try to execute this query directly to your database:
>
> > ALTER TABLE
> > sf_guard_group_permission ADD CONSTRAINT
> > sf_guard_group_permi
