|
Size: | 50650 |
Storage flags: | no_autoload,compress/gzip (15%) |
The Table service offers structured storage in the form of tables.
Table Storage is offered by Windows Azure as a REST API which is wrapped by the ZendService\WindowsAzure\Storage\Table class in order to provide a native PHP interface to the storage account.
This topic lists some examples of using the ZendService\WindowsAzure\Storage\Table class. Other features are available in the download package, as well as a detailed API documentation of those features.
Note that development table storage (in the Windows Azure SDK) does not support all features provided by the API. Therefore, the examples listed on this page are to be used on Windows Azure production table storage.
This topic lists some samples of operations that can be executed on tables.
Using the following code, a table can be created on Windows Azure production table storage.
Creating a table
1 2 3 4 5 6 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$result = $storageClient->createTable('testtable');
echo 'New table name is: ' . $result->Name;
|
Using the following code, a list of all tables in Windows Azure production table storage can be queried.
Listing all tables
1 2 3 4 5 6 7 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$result = $storageClient->listTables();
foreach ($result as $table) {
echo 'Table name is: ' . $table->Name . "\r\n";
}
|
Tables store data as collections of entities. Entities are similar to rows. An entity has a primary key and a set of properties. A property is a named, typed-value pair, similar to a column.
The Table service does not enforce any schema for tables, so two entities in the same table may have different sets of properties. Developers may choose to enforce a schema on the client side. A table may contain any number of entities.
ZendService\WindowsAzure\Storage\Table provides 2 ways of working with entities:
All examples will make use of the following enforced schema class.
Enforced schema used in samples
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | class SampleEntity extends ZendService\WindowsAzure\Storage\TableEntity
{
/**
* @azure Name
*/
public $Name;
/**
* @azure Age Edm.Int64
*/
public $Age;
/**
* @azure Visible Edm.Boolean
*/
public $Visible = false;
}
|
Note that if no schema class is passed into table storage methods, ZendService\WindowsAzure\Storage\Table automatically works with ZendService\WindowsAzure\Storage\DynamicTableEntity.
To enforce a schema on the client side using the ZendService\WindowsAzure\Storage\Table class, you can create a class which inherits ZendService\WindowsAzure\Storage\TableEntity. This class provides some basic functionality for the ZendService\WindowsAzure\Storage\Table class to work with a client-side schema.
Base properties provided by ZendService\WindowsAzure\Storage\TableEntity are:
Here’s a sample class inheriting ZendService\WindowsAzure\Storage\TableEntity:
Sample enforced schema class
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | class SampleEntity extends ZendService\WindowsAzure\Storage\TableEntity
{
/**
* @azure Name
*/
public $Name;
/**
* @azure Age Edm.Int64
*/
public $Age;
/**
* @azure Visible Edm.Boolean
*/
public $Visible = false;
}
|
The ZendService\WindowsAzure\Storage\Table class will map any class inherited from ZendService\WindowsAzure\Storage\TableEntity to Windows Azure table storage entities with the correct data type and property name. All there is to storing a property in Windows Azure is adding a docblock comment to a public property or public getter/setter, in the following format:
Enforced property
1 2 3 4 | /**
* @azure <property name in Windows Azure> <optional property type>
*/
public $<property name in PHP>;
|
Let’s see how to define a property “Age” as an integer on Windows Azure table storage:
Sample enforced property
1 2 3 4 | /**
* @azure Age Edm.Int64
*/
public $Age;
|
Note that a property does not necessarily have to be named the same on Windows Azure table storage. The Windows Azure table storage property name can be defined as well as the type.
The following data types are supported:
To use the ZendService\WindowsAzure\Storage\Table class without defining a schema, you can make use of the ZendService\WindowsAzure\Storage\DynamicTableEntity class. This class inherits ZendService\WindowsAzure\Storage\TableEntity like an enforced schema class does, but contains additional logic to make it dynamic and not bound to a schema.
Base properties provided by ZendService\WindowsAzure\Storage\DynamicTableEntity are:
Other properties can be added on the fly. Their Windows Azure table storage type will be determined on-the-fly:
Dynamically adding properties ZendServiceWindowsAzureStorageDynamicTableEntity
1 2 3 4 5 | $target = new ZendService\WindowsAzure\Storage\DynamicTableEntity(
'partition1', '000001'
);
$target->Name = 'Name'; // Will add property "Name" of type "Edm.String"
$target->Age = 25; // Will add property "Age" of type "Edm.Int32"
|
Optionally, a property type can be enforced:
Forcing property types on ZendServiceWindowsAzureStorageDynamicTableEntity
1 2 3 4 5 6 7 8 | $target = new ZendService\WindowsAzure\Storage\DynamicTableEntity(
'partition1', '000001'
);
$target->Name = 'Name'; // Will add property "Name" of type "Edm.String"
$target->Age = 25; // Will add property "Age" of type "Edm.Int32"
// Change type of property "Age" to "Edm.Int32":
$target->setAzurePropertyType('Age', 'Edm.Int64');
|
The ZendService\WindowsAzure\Storage\Table class automatically works with ZendService\WindowsAzure\Storage\TableEntity if no specific class is passed into Table Storage methods.
Using the following code, an entity can be inserted into a table named “testtable”. Note that the table has already been created before.
Inserting an entity
1 2 3 4 5 6 7 8 9 10 11 12 13 | $entity = new SampleEntity ('partition1', 'row1');
$entity->FullName = "Maarten";
$entity->Age = 25;
$entity->Visible = true;
$storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$result = $storageClient->insertEntity('testtable', $entity);
// Check the timestamp and etag of the newly inserted entity
echo 'Timestamp: ' . $result->getTimestamp() . "\n";
echo 'Etag: ' . $result->getEtag() . "\n";
|
Using the following code, an entity can be retrieved by partition key and row key. Note that the table and entity have already been created before.
Retrieving an entity by partition key and row key
1 2 3 4 5 6 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$entity= $storageClient->retrieveEntityById(
'testtable', 'partition1', 'row1', 'SampleEntity'
);
|
Using the following code, an entity can be updated. Note that the table and entity have already been created before.
Updating an entity
1 2 3 4 5 6 7 8 9 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$entity = $storageClient->retrieveEntityById(
'testtable', 'partition1', 'row1', 'SampleEntity'
);
$entity->Name = 'New name';
$result = $storageClient->updateEntity('testtable', $entity);
|
If you want to make sure the entity has not been updated before, you can make sure the Etag of the entity is checked. If the entity already has had an update, the update will fail to make sure you do not overwrite any newer data.
Updating an entity (with Etag check)
1 2 3 4 5 6 7 8 9 10 11 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$entity = $storageClient->retrieveEntityById(
'testtable', 'partition1', 'row1', 'SampleEntity'
);
$entity->Name = 'New name';
// last parameter instructs the Etag check:
$result = $storageClient->updateEntity('testtable', $entity, true);
|
Using the following code, an entity can be deleted. Note that the table and entity have already been created before.
Deleting an entity
1 2 3 4 5 6 7 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$entity = $storageClient->retrieveEntityById(
'testtable', 'partition1', 'row1', 'SampleEntity'
);
$result = $storageClient->deleteEntity('testtable', $entity);
|
Queries in ZendService\WindowsAzure\Storage\Table table storage can be performed in two ways:
Using the following code, a table can be queried using a filter condition. Note that the table and entities have already been created before.
Performing queries using a filter condition
1 2 3 4 5 6 7 8 9 10 11 12 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$entities = $storageClient->storageClient->retrieveEntities(
'testtable',
'Name eq \'Maarten\' and PartitionKey eq \'partition1\'',
'SampleEntity'
);
foreach ($entities as $entity) {
echo 'Name: ' . $entity->Name . "\n";
}
|
Using the following code, a table can be queried using a fluent interface. Note that the table and entities have already been created before.
Performing queries using a fluent interface
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$entities = $storageClient->storageClient->retrieveEntities(
'testtable',
$storageClient->select()
->from($tableName)
->where('Name eq ?', 'Maarten')
->andWhere('PartitionKey eq ?', 'partition1'),
'SampleEntity'
);
foreach ($entities as $entity) {
echo 'Name: ' . $entity->Name . "\n";
}
|
This topic demonstrates how to use the table entity group transaction features provided by Windows Azure table storage. Windows Azure table storage supports batch transactions on entities that are in the same table and belong to the same partition group. A transaction can include at most 100 entities.
The following example uses a batch operation (transaction) to insert a set of entities into the “testtable” table. Note that the table has already been created before.
Executing a batch operation
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
// Start batch
$batch = $storageClient->startBatch();
// Insert entities in batch
$entities = generateEntities();
foreach ($entities as $entity) {
$storageClient->insertEntity($tableName, $entity);
}
// Commit
$batch->commit();
|
When running a PHP application on the Windows Azure platform in a load-balanced mode (running 2 Web Role instances or more), it is important that PHP session data can be shared between multiple Web Role instances. The Windows Azure SDK for PHP provides the ZendService\WindowsAzure\SessionHandler class, which uses Windows Azure Table Storage as a session handler for PHP applications.
To use the ZendService\WindowsAzure\SessionHandler session handler, it should be registered as the default session handler for your PHP application:
Registering table storage session handler
1 2 3 4 5 6 7 8 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$sessionHandler = new ZendService\WindowsAzure\SessionHandler(
$storageClient , 'sessionstable'
);
$sessionHandler->register();
|
The above classname registers the ZendService\WindowsAzure\SessionHandler session handler and will store sessions in a table called “sessionstable”.
After registration of the ZendService\WindowsAzure\SessionHandler session handler, sessions can be started and used in the same way as a normal PHP session:
Using table storage session handler
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | $storageClient = new ZendService\WindowsAzure\Storage\Table(
'table.core.windows.net', 'myaccount', 'myauthkey'
);
$sessionHandler = new ZendService\WindowsAzure\SessionHandler(
$storageClient , 'sessionstable'
);
$sessionHandler->register();
session_start();
if (!isset($_SESSION['firstVisit'])) {
$_SESSION['firstVisit'] = time();
}
// ...
|
Warning
The ZendService\WindowsAzure\SessionHandler session handler should be registered before a call to session_start() is made!
The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed.