Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Added composite primary key support to JTable. #1606

merged 4 commits into from

10 participants

ianmacl Louis Landry Matias Griese Md Rashidul Islam Chad Windnagle Sam Moffatt Michael Babker Andrew Eddie elinw Viet Hoang Vu

No description provided.

ianmacl ianmacl closed this
ianmacl ianmacl reopened this
Louis Landry

Would you mind double checking the code style on this? The pull tester shows 2 more issues than most other ones, and I'd like to be sure. Marked it for 12.3 regardless. I'd also like to leave it open for a few days in case others want to comment.


I used underscores on protected variables to avoid colliding with columns in the table.

((12 lines not shown))
* Object constructor to set table and key fields. In most cases this will
* be overridden by child classes to explicitly set the table and key fields
* for a particular database table.
* @param string $table Name of the table to model.
- * @param string $key Name of the primary key field in the table.
+ * @param array $key Name of the primary key field in the table.

Should key be mixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

You are right @eddieajau. I have changed it to mixed.

((19 lines not shown))
* @param JDatabaseDriver $db JDatabaseDriver object.
* @since 11.1
- public function __construct($table, $key, JDatabaseDriver $db)

Any particular reason you are dropping the type hinting here?

ianmacl added a note

To save disk space. :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Matias Griese

Nice -- but as we are on it, I would like to allow one more use case, which is using "foreign key" as a primary key. For example UCM could be implemented by extending a table with another table using the same key.

I would also make a small feature to allow table to know if item already exists in the table. We have implementation of this feature in Kunena and it would be really easy to add into here, too. Basically you need to add:

protected $_exists = false;

public function exists($exists = null)
    $return = $this->_exists;
    if ($exists !== null)
        $this->_exists = $exists;
    return $return;

.. and some logic to set the variable when the item gets loaded, saved or removed.

Above code also prevents extra lookup to the database if the item was fetched earlier. If you want to handle both, I would set $_exists = null at first and use true/false when you want to know the status of the object (also change the code to make SQL query if state is unknown).


@mahagr Those are good ideas and definitely worth exploring. I'd like to get things in as is first and then we can build on it. I think what is there provides a good foundation that we can build on.

Louis Landry LouisLandry Merge pull request #1627 from elkuku/patch-5
Correct a class name JLoggerCallback => JLogLoggerCallback
ianmacl ianmacl closed this
ianmacl ianmacl reopened this

Rebased, squashed and fixed doc block issues.

Louis Landry LouisLandry merged commit 586e826 into from

@mahagr I hope you follow up with a pull request with some of the ideas that you had.

Matias Griese

@ianmacl Our house is currently under repair (water pipes...), which unfortunately has a small distracting effect on everything I (try to) do.

Are you coming to world conference?

Md Rashidul Islam

doesn't included with Joomla 2.5.7 :-1:

Chad Windnagle

@rashidul04 this is the platform, so the CMS may or may not implement the platform changes back to the CMS. If they do, it usually takes longer, and will not make it into the 2.5.x series.

Sam Moffatt

It'll be in Platform 12.3's release which will likely be picked up with the Joomla CMS 3.1 release. You can ship it and load it yourself with 2.5/3.0 and just give it another name so that it doesn't conflict.

Michael Babker

Unfortunately, it looks like there was an unintended regression here dealing with the asset handling in JTable::store(). It looks like the problem can be chased down to where the $this->_tbl_key was changed to $this->_tbl_keys since JDatabaseDriver::insertObject() expects that param to be a string, not an array. This causes the ID (or whatever the key(s) may be) of the newly inserted record to not be stored in the JTable instance, meaning when $this->_getAssetName(); is called a few lines later, the last part of the name is .0 instead of the value of the key.


Asset parent tables are not necessarily JTables i.e. #__extensions

diesl diesl referenced this pull request in jemproject/JEM-Project

Import of exported cat_events doesn't work #60

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Oct 21, 2012
  1. Viet Hoang Vu
Commits on Oct 22, 2012
  1. Louis Landry

    Merge pull request #1626 from vietvh/postgresql

    LouisLandry authored
    Fix broken module installation in Postgresql because of NULL constraint
  2. Louis Landry

    Merge pull request #1627 from elkuku/patch-5

    LouisLandry authored
    Correct a class name JLoggerCallback => JLogLoggerCallback
Commits on Oct 23, 2012
  1. ianmacl
Something went wrong with that request. Please try again.