Download the PHP package adnane/simple-uuid without Composer
On this page you can find all versions of the php package adnane/simple-uuid. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download adnane/simple-uuid
More information about adnane/simple-uuid
Files in adnane/simple-uuid
Package simple-uuid
Short Description a simple laravel package to generate uuid instead of auto increment ids as primary keys
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package simple-uuid
Simple Uuid
a simple laravel package to generate uuid instead of auto incrementing ids as primary keys.
what's even a uuid?
UUID stands for Universally Unique IDentifier. as you may encounter the acronym of it GUID (Globally Unique IDentifier).
It’s a 16 bytes Worldwide unique number! And absolulty, without using any kind of central authority or any external APIS. Actually, the way it is generated, following a standardized algorithm, ensures that every UUID is unique. and kinda impossible to generate the exact same UUID as another one somewhere else in the whole world.
and generally, it's something that looks like this:
but, why do you even need to use it and not just the auto incrementing ids?
well, it's not fair to just say that you always need to use the UUID thing istead of auto incrementing ids to index your objects in your database. but it's something cool to know the different uses of both of them and choose depending on your needs.
here are some reasons why you should use UUIDs:
-
security: and definitely this is because uuids are impossible to guess, which is not like auto incrementing ids.
-
concerning database scaling: Imagine you’ve been writing blog articles on two self-hosted blogging platforms. And for some reason you want to merge those two blogs into one. If you had used usual auto-incrementing IDs, you would have to re-index every blog post of the databases and update every foreign key that might point to them. But if you had used UUID as primary key, No work to do!
- local-first applications! : Let’s say I have a collaborative application. And I want to be able to work with that application, event when I’m offline. And that means creating new content that should be added to the common database. What I expect is for the application to let me create my new content, and merge it to the central shared database when I’m back online. And I expect my coworkers to be able to do the same. In this scenario, entries in the database can’t be indexed with an auto incrementing number. Because my coworkers and myself, while offline, would be creating entries with the same ID. And once back online, we would face numerous data merging issues. UUID in this case, is a marvelous solution!
installation
Warning: This package is not installable via Composer 1.x, make sure you upgrade to Composer 2+ before trying to install it.
using composer:
the package's service provider is auto loaded so no need to add it in the providers array in app.php .actually, you may need to define an alias for the package's trait , in your app.php in the aliases array as bellow:
use
as this package destined for simple use you can simply just:
-
import the package's trait inside the model that you want to use uuid on:
-
add it to the model class:
-
update your target migration file:
-
run laravel migrations
-
store a dummy record & check out stored id:
- use as foreign key
contributing
everyone is welcome :)
