Skip to content

Correct some writtig errors #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AbdellahBoutmad wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Correct some writtig errors #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 23 additions & 23 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,36 +13,36 @@ Helps you convert every SQL [nullable](https://www.w3schools.com/sql/sql_null_va
## Features
- 100% [GORM](https://gorm.io/) support
- Can be marshalled into JSON
- Can be unmarshal from JSON
- Can be unmarshalled from JSON
- Convenient Set/Get operation
- Support MySQL, MariaDB, SQLite, and PostgreSQL
- Zero configuration, just use it as normal data type.
- Heavily tested! So you don't have to worry of many bugs :D
- Zero configuration, just use it as a normal data type.
- Heavily tested! So you don't have to worry about many bugs :D

## Supported Data Types
- bool
- byte
- string
- time.Time (capable of handling `DATETIME`, `TIME`, `DATE`, and `TIMESTAMP`)
- []byte
- float32
- float64
- int
- int8
- int16
- int32
- int64
- uint
- uint8
- uint16
- uint32
- uint64

**WARNING:** PostgreSQL [won't support any form of unsigned integers](https://www.postgresql.org/message-id/CAEcSYX+Arn7y4FeYPp6ZgbiiiMfZYmsn9aUyotZB-MA1n5hTOw@mail.gmail.com). However, you still able to use any uint variants with a drawback: **they will be stored in form of raw binary instead of normal integer**. Thus, PostgreSQL-side uint comparation is impossible, you have to compare them in your Go application. MySQL, MariaDB, and SQLite won't affected by this issue, don't worry.
- `bool`
- `byte`
- `string`
- `time.Time` (capable of handling `DATETIME`, `TIME`, `DATE`, and `TIMESTAMP`)
- `[]byte`
- `float32`
- `float64`
- `int`
- `int8`
- `int16`
- `int32`
- `int64`
- `uint`
- `uint8`
- `uint16`
- `uint32`
- `uint64`

**WARNING:** PostgreSQL [won't support any form of unsigned integers](https://www.postgresql.org/message-id/CAEcSYX+Arn7y4FeYPp6ZgbiiiMfZYmsn9aUyotZB-MA1n5hTOw@mail.gmail.com). However, you can still use any `uint` variants with a drawback: **they will be stored in raw binary form instead of normal integer**. Thus, PostgreSQL-side `uint` comparison is impossible; you have to compare them in your Go application. MySQL, MariaDB, and SQLite are unaffected by this issue.

# How to Use?

Very easy! first of all, let's install like normal Go packages
Very easy! First, let's install like normal Go packages:

```bash
go get github.com/tee8z/nullable
Expand Down