Hi Adrian
Is this still true for Cake 1.2.x.x ?
Given the trac link that I posted, I think it is unlikely that you will
find support for it in 1.2.
You might find this article interesting. It is about surrogate primary
key ( 'id' - integer )
which are sometimes convenient (from a
On 2/27/07, AD7six [EMAIL PROTECTED] wrote:
On Feb 27, 8:42 am, Adrian Maier [EMAIL PROTECTED] wrote:
On 2/27/07, Langdon Stevenson [EMAIL PROTECTED] wrote:
My understanding is that Cake 1.1.x.x doesn't support multi-column keys.
This feature request in
Yes, I've read the article, and have been slowly hacking away at a
counter-article for a few months now. Wake up people, it's 2007, and
multi-column primary keys are *still* a dumb idea.
On Feb 27, 4:11 am, Langdon Stevenson [EMAIL PROTECTED]
wrote:
Hi Adrian
Is this still true for Cake
On 2/27/07, AD7six [EMAIL PROTECTED] wrote:
On Feb 27, 11:36 am, Adrian Maier [EMAIL PROTECTED] wrote:
On 2/27/07, AD7six [EMAIL PROTECTED] wrote:
On Feb 27, 8:42 am, Adrian Maier [EMAIL PROTECTED] wrote:
On 2/27/07, Langdon Stevenson [EMAIL PROTECTED] wrote:
My understanding
On Feb 27, 8:41 am, AD7six [EMAIL PROTECTED] wrote:
Does it? I always thought not including a unique index on a table's
data allowed duplicates.
And I feel that's all the article proves. The PK is for identifying a
row of data, a unique index is for preventing duplicates. There are
times
On Feb 27, 1:15 pm, nate [EMAIL PROTECTED] wrote:
Yes, I've read the article, and have been slowly hacking away at a
counter-article for a few months now. Wake up people, it's 2007, and
multi-column primary keys are *still* a dumb idea.
Here, here! compound primary key constraints are
That's an excellent point; differentiating the two is critical. The
typical argument against auto-incrementing primary keys is that they
have no symbolic meaning relative to the data. Even if that's true,
it's beside the point: it has inherent meaning within the application,
and that meaning
For example, we have table
user_id | text | date
--
1 | foo | 2007-02-27
Primary key is (user_id, date)
So, how can I use Model::save() in these cases? If I simply use is I
always get insert query and SQL error because of Primary key.
Now I see only one
Hi Pento
Pento wrote:
For example, we have table
user_id | text | date
--
1 | foo | 2007-02-27
Primary key is (user_id, date)
You either need to change the column name from user_id to id, or specify
the $primaryKey variable in your model to use
Hi, Langdon!
Thanks for fast answer.
var $primaryKey = user_id;
I know about this...But as you can see I have in SQL table Multicolumn
primary key, so
$primaryKey must be something like array(user_id, date);
Can CakePHP correctly work with multicolumn primary key in Model?
As I think, to
10 matches
Mail list logo
