mirror of
https://github.com/ramsey/uuid.git
synced 2026-06-14 15:56:48 +03:00
Fix Minor Typos in Docs
This commit is contained in:
+2
-2
@@ -101,7 +101,7 @@ this (again, assume some of the variables in this example have been set
|
||||
beforehand):
|
||||
|
||||
.. code-block:: php
|
||||
:caption: Store a string UUID to the uuid column
|
||||
:caption: Store UUID bytes to the uuid column
|
||||
:name: database.uuid-bytes-store-example
|
||||
|
||||
$sth->execute([
|
||||
@@ -186,7 +186,7 @@ with this approach, but there are a couple of points to consider:
|
||||
We'll deal with the first point in the section, :ref:`database.order`. For the
|
||||
second point, if you are using the string version of the UUID (i.e.,
|
||||
``char(36)``), then not only will the primary key be large and take up a lot of
|
||||
space, but every secondary key that uses that primary key will also be must
|
||||
space, but every secondary key that uses that primary key will also be much
|
||||
larger.
|
||||
|
||||
For this reason, if you choose to use UUIDs as primary keys, it might be worth
|
||||
|
||||
@@ -33,7 +33,7 @@ There are a lot of new features in ramsey/uuid! Here are a few of them:
|
||||
* :php:class:`Rfc4122\\UuidV3 <Ramsey\\Uuid\\Rfc4122\\UuidV3>`
|
||||
* :php:class:`Rfc4122\\UuidV4 <Ramsey\\Uuid\\Rfc4122\\UuidV4>`
|
||||
* :php:class:`Rfc4122\\UuidV5 <Ramsey\\Uuid\\Rfc4122\\UuidV5>`
|
||||
* Rfc4122\\NilUuid
|
||||
* :php:class:`Rfc4122\\NilUuid <Ramsey\\Uuid\\Rfc4122\\NilUuid>`
|
||||
|
||||
* Add classes to represent version 6 UUIDs, GUIDs, and nonstandard
|
||||
(non-RFC 4122 variants) UUIDs:
|
||||
|
||||
Reference in New Issue
Block a user