search

AshishJoshi-asj / zfdatagrid

Automatically exported from code.google.com/p/zfdatagrid
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Do not find how to specify the identifier column #174

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What is the expected output? What do you see instead?
my $grid->setDetailColumns() does not look to find the identifier column name.
Url ends like : /mode:view;[]/
Where identifier is detected ? Is there a mean to specify it manually ?

What version of the product are you using? On what operating system?
v6 alpha, under Linxu Fedora

Please provide any additional information below.

Original issue reported on code.google.com by tribal...@gmail.com on 16 Feb 2010 at 2:39

GoogleCodeExporter commented 9 years ago 
Hi,

Grid will look for the table primary key(s).

Does you table have hone?

Best Regards,
Bento Vilas Boas

Original comment by pao.fre...@gmail.com on 16 Feb 2010 at 3:43

GoogleCodeExporter commented 9 years ago 
My table has no primary key for the moment (it is generated via PHP). But I can
change this behaviour in my case.
Could it not be interesting to be able to specify oneself the field we want to 
be
consider as primary on (if not user defined, so the detected primary key will 
be used) ?

Original comment by tribal...@gmail.com on 17 Feb 2010 at 10:05

GoogleCodeExporter commented 9 years ago 
Mistake ! I have a primary key for this table. And so, it seems not to be 
detected...

Original comment by tribal...@gmail.com on 17 Feb 2010 at 10:42

GoogleCodeExporter commented 9 years ago 
Hm,

That's odd...

I'm using the Zend_Db_Table_Abstract describeTable() to find tables primary key.

Even if your table doesn't have a PK, Zend_Db will look for a unique index and 
return
it as PK

Can you send me your ddl and your grid construct?

You can email me, if don't want to post it publicly geral[the symbol we
know]petala-azul.com

Best Regards,
Bento Vilas Boas

Original comment by pao.fre...@gmail.com on 17 Feb 2010 at 4:15

GoogleCodeExporter commented 9 years ago 
Issue can be closed, it is resolved since revision 640 (linked to issue 180)

Original comment by tribal...@gmail.com on 23 Feb 2010 at 10:30

GoogleCodeExporter commented 9 years ago

Original comment by pao.fre...@gmail.com on 23 Feb 2010 at 2:52

GoogleCodeExporter commented 9 years ago

Original comment by bento.vi...@gmail.com on 3 Mar 2010 at 4:56