ThinkPHP on Coinidea's Blog

[Push Notifications]Push Notifications Based on Umeng Service

Sun, 19 Nov 2017 11:48:10 +0000

When the server interacts with mobile clients, it often needs to push messages from the server to the user’s mobile device. Umeng provides such a push notification service — UPush.

Download the SDK code. Based on the demo, this article provides a simple ThinkPHP integration.

1
2
3
4
5
6


$appkey = "your app key";
$secret = "your app secret";
import('@.ORG.Notification');
$notification = new Notification($appkey, $secret);
$custom_data = array($key=>$value);
$notification->sendIOSBroadcast($your_title, $custom_data);

Notification.class.php is the demo.php from the SDK, encapsulated into ThinkPHP’s ORG folder.
If you have any questions, feel free to leave a comment below. I typically reply once a day.

[ThinkPHP]Table Locking Under Concurrency in ThinkPHP

Fri, 17 Nov 2017 03:10:04 +0000

Recently I needed to build a registration system that doesn’t require very high concurrency, but there’s still a possibility of multiple users registering at the same time. Since registration involves ordering, without row locking or table locking, the following situation can occur.
Example:
Currently the system only has user A registered with order 1, denoted as (A, 1).
At some moment t, users B, C, and D register simultaneously. The backend receives all three requests almost at the same time, queries the registration table, finds only (A, 1), and inserts (B, 2), (C, 2), (D, 2) into the table, resulting in:

1
2
3
4


(A, 1)
(B, 2)
(C, 2)
(D, 2)

My initial idea was: instead of recording the order number, I would record the insertion timestamp, which would give:

1
2
3
4


(A, ta)
(B, tb)
(C, tc)
(D, td)

ta, tb, tc, td are almost impossible to be equal.
However, this approach has three unsolvable issues:

There is a (very low) probability that timestamps could be equal
It’s not intuitive and requires sorting by timestamp
Registration has a capacity limit (e.g., 40 spots) and needs to immediately report whether the registration was successful

The current solution is to use database locking.
After researching online, ThinkPHP supports both pessimistic and optimistic locking. Given the low traffic of the target system, pessimistic locking is sufficient.

MyISAM can only lock tables, while InnoDB supports row-level locking. Table locking is sufficient for the target system.
The official documentation provides this table locking approach:

1

$User->lock(true)->save($data);// Use pessimistic locking

However, the target system needs to perform a series of operations, so the table locking code used is:

1
2
3
4


M()->query("lock tables yourtable write");
// TODO
// your code
M()->query("unlock tables");

The actual results worked quite well [real dates have been redacted]:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40


??-??-?? 10:00:00 1
??-??-?? 10:00:00 2
??-??-?? 10:00:00 3
??-??-?? 10:00:00 4
??-??-?? 10:00:01 5
??-??-?? 10:00:01 6
??-??-?? 10:00:01 7
??-??-?? 10:00:01 8
??-??-?? 10:00:02 9
??-??-?? 10:00:02 10
??-??-?? 10:00:02 11
??-??-?? 10:00:02 12
??-??-?? 10:00:02 13
??-??-?? 10:00:02 14
??-??-?? 10:00:03 15
??-??-?? 10:00:03 16
??-??-?? 10:00:03 17
??-??-?? 10:00:05 18
??-??-?? 10:00:06 19
??-??-?? 10:00:07 20
??-??-?? 10:00:08 21
??-??-?? 10:00:10 22
??-??-?? 10:00:15 23
??-??-?? 10:00:17 24
??-??-?? 10:00:19 25
??-??-?? 10:00:19 26
??-??-?? 10:00:24 27
??-??-?? 10:00:25 28
??-??-?? 10:00:34 29
??-??-?? 10:00:35 30
??-??-?? 10:00:38 31
??-??-?? 10:01:06 32
??-??-?? 10:01:11 33
??-??-?? 10:01:11 34
??-??-?? 10:01:17 35
??-??-?? 10:01:18 36
??-??-?? 10:02:27 37
??-??-?? 10:02:38 38
??-??-?? 10:02:39 39
??-??-?? 10:02:57 40

[PHP] Large-Scale Data Import and Export with ThinkPHP, PHP, and MySQL

Thu, 08 Dec 2016 09:37:45 +0000

Large-Scale Data Import and Export

Note: “Large-scale” here refers to importing and exporting 100,000+ records from text files (including Office documents such as docx, xlsx).

MySQL has two very common table types: MyISAM and InnoDB. There are many comparisons of these two types online. The main difference is that InnoDB supports transactions and row-level locking, while MyISAM does not. MyISAM is relatively more efficient, and each has its own advantages and disadvantages.

Use Cases for MyISAM and InnoDB

MyISAM is suitable for:

Frequent COUNT calculations;
Infrequent inserts but frequent queries;
No transactions needed.

InnoDB is suitable for:

High reliability requirements or transaction support needed;
Frequent table updates and queries with high likelihood of table locking.

Differences Between MyISAM and InnoDB

MyISAM does not support advanced features like transactions, while InnoDB does.
MyISAM tables do not support foreign keys.
During write operations (insert, update, delete), MyISAM locks the entire table, while InnoDB locks only the affected rows.
When your database has heavy writes, updates, and deletions with relatively few queries, or when data integrity requirements are high, choose InnoDB. When your database is primarily read-heavy with relatively few updates and writes, and data integrity requirements are less strict, choose MyISAM, as its query performance is faster than InnoDB.

In summary, InnoDB is a good choice for this scenario.

Optimization Methods for Inserting Large Amounts of Data

When PHP needs to insert large amounts of data, inserting one record at a time results in severe I/O performance bottlenecks.

Demo Code:

1
2
3
4
5
6
7


$params = array('value' => '50');
set_time_limit(0);
echo date("H:i:s");
for($i = 0; $i < 2000000; $i++) {
 $connect_mysql->insert($params);
}
echo date("H:i:s");

There are two methods to solve this problem:

1. Using Transactions (InnoDB supported)

For example, you can commit a transaction every 10,000 or 100,000 records, which greatly reduces I/O.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


echo date("H:i:s");
$connect_mysql->query('BEGIN');
$params = array('value' => '50');
for($i = 0; $i < 2000000; $i++) {
 $connect_mysql->insert($params);
 if($i % 100000 == 0) {
 $connect_mysql->query('COMMIT');
 $connect_mysql->query('BEGIN');
 }
}
$connect_mysql->query('COMMIT');
echo date("H:i:s");

2. SQL Statement Concatenation

This is a MySQL feature that uses optimized SQL statements: concatenate SQL statements using insert into table () values (),(),(),() and insert them all at once. If the string is too long, you need to configure MySQL by running:

1

SET GLOBAL max_allowed_packet = 2 * 1024 * 1024 * 10;

1
2
3
4
5
6


$sql = "INSERT INTO twenty_million (value) VALUES";
for($i = 0; $i < 2000000; $i++) {
 $sql .= "('50'),";
}
$sql = substr($sql, 0, strlen($sql) - 1);
$connect_mysql->query($sql);

The first method is more commonly used, while the second is mostly for test data.

By default, PHP has a memory limit of 128MB. When ThinkPHP exceeds this memory limit, you can either increase PHP’s default maximum memory or simply remove the APP_DEBUG constant definition in the entry file or set it to false. This will save a lot of memory. Of course, you can also use transaction mode to commit every n records. ThinkPHP’s addAll function can also be used for batch inserts, though it has quite a few bugs.

Starting and Committing Transactions in ThinkPHP

1
2


$table->startTrans();
$table->commit();

When working with Office files, PHPWord and PHPExcel are recommended.

[PHP] Configuring PHPUnit for ThinkPHP

Thu, 10 Dec 2015 14:19:57 +0000

Version Details

PHP: 5.3

PHPUnit

ThinkPHP 3.1.3

IDE: PHPStorm 10 (recommended)

Configuring PHPUnit in PHPStorm

See the blog post:

http://blog.coinidea.com/web开发/php-1088.html

ThinkPHP Deployment

Official code download:

http://www.thinkphp.cn/down.html

Site initialization:

http://www.thinkphp.cn/info/60.html

Test Cases

In this example, the index.php in the root directory is configured as follows:

1
2
3
4
5
6
7


<?php
define('APP_NAME', 'example');
define('APP_PATH', '../example/');
define('APP_PHPUNIT', false);
define('APP_DEBUG', true);
require('../ThinkPHP/ThinkPHP.php');
?>

After the first visit, the following directory structure is generated:

Create a new folder named “Testcase” in the example site.

Testing the Model

Create HelloModel.class.php:

1
2
3
4
5
6
7
8
9


<?php
class HelloModel extends Model
{
 public function sayHello()
 {
 print 'Hello';
 return 'Hello';
 }
}

Create a Test.php file in the Test folder as the PHPUnit test file. Note that you need to require ThinkPHP to initialize the framework environment. Also, in Think.class.php, modify the

start() function by changing App::run() to !APP_PHPUNIT && App::run();

This distinguishes between site runtime and test case execution.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


<?php
define('APP_NAME', 'example');
define('APP_PATH', './../../example/');
define('APP_PHPUNIT', true);
require('./../../ThinkPHP/ThinkPHP.php');
class TestSayHello extends PHPUnit_Framework_TestCase {

public function setUp() { }

public function tearDown(){ }

}

Add a test case in TestSayHello:

1
2
3
4
5


public function testHelloModel()
{
 $hello = D('Hello');
 $this->assertTrue($hello->sayHello('Hello') == 'Hello');
}

Testing the Action

Modify IndexAction.class.php as follows:

1
2
3
4
5
6
7
8
9


<?php
class IndexAction extends Action
{
 public function index()
 {
 $hello = D("Hello");
 return $hello->sayHello();
 }
}

Browser access to Index:

Add a test case in TestSayHello:

1
2
3
4
5


public function testHelloAction()
{
 $hello = new IndexAction();
 $this->assertTrue($hello->index() == 'Hello');
}

Results

Running Test.php produces the following result:

Tests passed. At this point, unit testing has been successfully added to ThinkPHP.

poisonbian 2016/05/10 14:57

I tried following this guide and found that the model couldn’t be used, and custom functions in the Common directory were not loaded. After some investigation, I think adding the APP_PHPUNIT check in Think.class.php is not ideal. It would be better to add it in App.class.php instead: !APP_PHPUNIT && App::exec();