edwingeng/wuid

An extremely fast globally unique number generator.

wuid's Issues

在32位系统上编译报错

我使用 GO111MODULE=on GOARCH=386 来编译，报空指针：

问下啊，ID是趋势递增的么

问下啊，ID是趋势递增的么？

为什么将返回结果从uint64改成了int64呢？

为什么将返回结果从uint64改成了int64呢？

callback method after restart

If the process is restarted, the callback method is high 28, is it possible to repeat the id

请问高28位超过后，有什么解决方案？

2^64总量始终有限，低36位用完可以更新高28位+1，当高位超过后，有什么解决方案？

兵哥，tag参数是做什么用的啊

兵哥，tag参数是做什么用的啊

Are the IDs generated time sortable?

Are the IDs generated time sortable?

请问一下,如果不同机房,通过设置Section ID可以实现跨机房全局唯一吗

// A机房
once.Do(func() {
	g=wuid.NewWUID("default",nil,wuid.WithSection(1))
        g.LoadH24FromMysql(....
})
// B机房
once.Do(func() {
	g=wuid.NewWUID("default",nil,wuid.WithSection(2))
        g.LoadH24FromMysql(....
})
// 然后g在程序中作为全局变量,这样,两个g都不共享mysql,可以达到全局唯一吗

能否把go-redis依赖调整到最新v8版本

现在项目本身在使用最新v8版本，然后又需要单独实例化一个v6版本

调用wuid生成id后，会自动关闭数据库连接，导致后续数据库操作无法继续执行

调用wuid生成id后，会自动关闭数据库连接，导致后续数据库操作无法继续执行
package tools
import (

"database/sql"
"github.com/astaxie/beego/orm"
"github.com/edwingeng/wuid/mysql"
_"github.com/go-sql-driver/mysql"

)

var newDB = func() (*sql.DB,bool,error){
db,_ := orm.GetDB()
return db,true,nil
}

var g = wuid.NewWUID("default", nil)

func NewId() (uint64){
g.LoadH28FromMysql(newDB, "wuid")
return g.Next()
}

调用代码：

func AddUser(u *User) (int64, error) {
// db,err := orm.GetDB()
//fmt.Println(err)
o := orm.NewOrm()
u.Id = 74837477878
for i:=0;i<100;i++ {
fmt.Println(tools.NewId())
}

fmt.Println(u)
return o.Insert(u)

}

插入操作无法继续执行，
[ORM]2019/05/12 22:09:56 -[Queries/default] - [FAIL / db.Exec / 0.0ms] - [INSERT INTO sys_user (id, username, password, phone, email, name, avatar, salt, status, is_staff, last_login_time, login_error_times, remark, delete_flag, create_by, create_time, update_by, update_time) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)] - 74837477878, qingmumao,
xxxxxxxx, 13332978703, [email protected], , , , `0`, `0`, `0`, `0`, , 0, 0, 0, 0, 0 - sql: database is closed

optimize too many tables in mysql question

this wuid design make too many tables in mysql .

What about segmentio/ksuid?

What about https://github.com/segmentio/ksuid?

请问这个id 生成器是有序的吗？

这个id生成器是有序的吗？我需要做排序

请问wuid生成的id拿来做主键合适吗

假如用wuid来表示一个订单的ID, 存储到数据里里面推荐用它的字符串表示还是直接用数字呢?
如果存储的是数字, wuid返回uint64类型, 拿来做主键合适吗?

Document expected behaviour of floor

The behaviour of how the floor impacts the output isn't really documented and the term itself brings confusion.

From https://en.wikipedia.org/wiki/Floor_and_ceiling_functions :

In mathematics and computer science, the floor function is the function that takes as input a real number x, and gives as output the greatest integer less than or equal to x.

Based on this definition, when I specified a step of 1024 with a floor of 897 and H28 of 1 I didn't expect to receive a value of 0x00000010000003a7 followed by 0x0000001000000728 and 0x0000001000000aa9; given that 0xAA9 is much higher than the "floor" value. It's obvious why this is happening when looking at the code where next() returns n / floor * floor.

The best that I can see is this is somehow useful in order to make it less obvious what the "step" actually is, using a Real number as step and benefiting from rounding to nearest Integer, causing the steps to be +/- 1. A floor > 1 is also a requirement when used with obfuscation to hide the obfuscation values used.

However the main issue is that I couldn't find any documentation about this expected behaviour, so as a user of this library I ended up having to dig through the code to figure it out.