9 Commits

Author	SHA1	Message	Date
Brandon Kelly	e6f5c46cdc	Fixes #15633: Deprecate some things going away/changing in 2.1 ... - Deprecated `yii\base\BaseObject::className()` in favor of native PHP syntax `::class`, which does not trigger autoloading - Deprecated XCache and Zend data cache support as caching backends - Deprecated `yii\BaseYii::powered()` method - Added `yii\base\InvalidArgumentException` and deprecated `yii\base\InvalidParamException` - Added `yii\BaseYii::debug()` and deprecated `yii\BaseYii::trace()`	2018-02-11 01:48:29 +03:00
Carsten Brandt	f259eadf7a	be clear about timeout in seconds in Mutex ... fixes https://github.com/yiisoft/yii2/issues/15030	2017-10-27 09:46:11 +02:00
Alexander Makarov	1f26db9fb7	Applied code style fixes	2017-07-21 15:42:06 +03:00
Carsten Brandt	445019779f	Fixes #14206: MySqlMutex, PgsqlMutex and OracleMutex now use useMaster() to ensure lock is aquired on the same DB server	2017-07-13 09:52:38 +03:00
Kolyunya	924a3edf4b	Remove excessive use statements	2017-02-15 20:14:53 +03:00
Robert Korulczyk	4aa935e69e	Fixes #12055: Changed boolean to bool and integer to int in phpdoc	2016-11-07 02:51:39 +03:00
Carsten Brandt	e05f55bd13	Update PgsqlMutex.php ... fixed `@since` annotation.	2016-04-05 04:53:52 +02:00
Yaroslav Lukyanov	db1a96d876	Added tests for #8920, used 16bit integers to avoid out of range error	2016-04-05 00:57:52 +03:00
John Was	84f37705bf	Fixes #8920: Added yii\mutex\PgsqlMutex which implements mutex "lock" mechanism via PgSQL locks	2016-04-05 00:56:38 +03:00