


Analysis of the gtime module of the GoFrame framework and custom time formatting syntax
这篇文章给大家分享的内容是关于GoFrame框架之gtime时间模块和支持自定义时间格式化语法,有一定的参考价值,有需要的朋友可以参考一下。
通用时间管理模块,封装了常用的时间/日期相关的方法。并支持自定义的日期格式化语法,格式化语法类似PHP的date语法。
使用方式:
import "gitee.com/johng/gf/g/os/gtime"
方法列表: godoc.org/github.com/johng-cn/gf/g/os/gtime
时间格式
gtime
模块最大的特点是支持自定义的时间格式,参考PHP日期时间格式语法,以下是支持的时间格式语法列表:
时间对象
方法列表:
type Time func New(t ...time.Time) *Time func NewFromStr(str string) *Time func NewFromStrFormat(str string, format string) *Time func NewFromStrLayout(str string, layout string) *Time func NewFromTime(t time.Time) *Time func NewFromTimeStamp(timestamp int64) *Time func Now() *Time func (t *Time) Add(d time.Duration) *Time func (t *Time) AddDate(years int, months int, days int) *Time func (t *Time) Clone() *Time func (t *Time) Format(format string) string func (t *Time) Layout(layout string) string func (t *Time) Local() *Time func (t *Time) Microsecond() int64 func (t *Time) Millisecond() int64 func (t *Time) Nanosecond() int64 func (t *Time) Round(d time.Duration) *Time func (t *Time) Second() int64 func (t *Time) String() string func (t *Time) ToLocation(location *time.Location) *Time func (t *Time) ToTime() time.Time func (t *Time) Truncate(d time.Duration) *Time func (t *Time) UTC() *Time
创建gtime.Time
对象可以通过标准库time.Time
对象、Unix时间戳、时间字符串(如:2018-07-18 12:01:00)、自定义时间字符串(需要给定格式,支持自定义格式及标准库格式)。
示例1,自定义时间格式化语法
package main import ( "fmt" "gitee.com/johng/gf/g/os/gtime" ) func main() { formats := []string{ "Y-m-d H:i:s.u", "D M d H:i:s T O Y", "\\T\\i\\m\\e \\i\\s: h:i:s a", "2006-01-02T15:04:05.000000000Z07:00", } t := gtime.Now() for _, f := range formats { fmt.Println(t.Format(f)) } }
在该示例中,我们给定了四种format格式,并将当前时间用这四种格式转换后打印出来。执行后,输出结果如下:
2018-07-22 11:17:13.797 Sun Jul 22 11:17:13 CST +0800 2018 Time is: 11:17:13 am 2006-01-02CST15:04:05.000000000Z07:00
可以看到,这个示例演示了几个需要注意的地方:
如果使用的字母与格式化字符冲突时,可以使用
\
符号转移该字符,这样时间格式解析器会认为该字符不是格式化字符,而是普通字母。因此这里的第三个字符串示例输出为:Time is: 11:17:13 am
使用
Format
方法接收的是自定义的时间格式化语法(如:Y-m-d H:i:s
),而不是标准库的事件格式语法(如:2006-01-02 15:04:05
),且两种语法不能混用,因此在这里的第四个字符串示例中原样输出参数值;
示例2,标准库时间格式化语法
package main import ( "fmt" "gitee.com/johng/gf/g/os/gtime" ) func main() { formats := []string{ "2006-01-02 15:04:05.000", "Mon Jan _2 15:04:05 MST 2006", "Time is: 03:04:05 PM", "2006-01-02T15:04:05.000000000Z07:00 MST", } t := gtime.Now() for _, f := range formats { fmt.Println(t.Layout(f)) } }
在该示例中,我们使用四种标准库的时间格式化语法格式化当前的时间并输出结果到终端。执行后,输出结果为:
2018-07-22 11:28:13.945 Sun Jul 22 11:28:13 CST 2018 Time is: 11:28:13 AM 2018-07-22T11:28:13.945153275+08:00 CST
根绝这个示例,也有几个需要说明的地方:
自定义时间格式化语法与标准库时间格式化语法并不冲突,前者使用
Format
方法,后者使用Layout
语法进行格式化,相互独立,互不冲突,无法混用;标准库的时间格式化语法自有特点,是不是感觉有点复杂;
示例3,时间对象链式操作
package main import ( "fmt" "gitee.com/johng/gf/g/os/gtime" "time" ) func main() { // 去年今日 fmt.Println(gtime.Now().AddDate(-1, 0, 0).Format("Y-m-d")) // 去年今日,UTC时间 fmt.Println(gtime.Now().AddDate(-1, 0, 0).Format("Y-m-d H:i:s T")) fmt.Println(gtime.Now().AddDate(-1, 0, 0).UTC().Format("Y-m-d H:i:s T")) // 下个月1号凌晨0点整 fmt.Println(gtime.Now().AddDate(0, 1, 0).Format("Y-m-d 00:00:00")) // 2个小时前 fmt.Println(gtime.Now().Add(-time.Hour).Format("Y-m-d H:i:s")) }
执行后,输出结果为:
2017-07-22 2017-07-22 11:42:36 CST 2017-07-22 03:42:36 UTC 2018-08-22 00:00:00 2018-07-22 10:42:36
该示例比较简单,便不多赘述。
工具方法
godoc.org/github.com/johng-cn/gf/g/os/gtime
func Date() string func Datetime() string func Microsecond() int64 func Millisecond() int64 func Nanosecond() int64 func Second() int64 func SetInterval(t time.Duration, callback func() bool) func SetTimeZone(zone string) error func SetTimeout(t time.Duration, callback func()) func StrToTime(str string) (time.Time, error) func StrToTimeFormat(str string, format string) (time.Time, error) func StrToTimeLayout(str string, layout string) (time.Time, error)
方法比较简单,比较常用的是以下几个方法;
Second
用于获得当前时间戳,Millisecond
、Microsecond
及Nanosecond
用于获得当前的毫秒、微秒和纳秒值;Date
和Datetime
用于获得当前日期及当前日期时间;SetTimeZone
用于设置当前进程的全局时区;其他方法说明请查看接口文档;
简单示例:
package main import ( "fmt" "gitee.com/johng/gf/g/os/gtime" ) func main() { fmt.Println("Date :", gtime.Date()) fmt.Println("Datetime :", gtime.Datetime()) fmt.Println("Second :", gtime.Second()) fmt.Println("Millisecond:", gtime.Millisecond()) fmt.Println("Microsecond:", gtime.Microsecond()) fmt.Println("Nanosecond :", gtime.Nanosecond()) }
执行后,输出结果为:
Date : 2018-07-22 Datetime : 2018-07-22 11:52:22 Second : 1532231542 Millisecond: 1532231542688 Microsecond: 1532231542688688 Nanosecond : 1532231542688690259
相关推荐:
自己搭建一个 Laravel 的 Docker的开发环境的方法
The above is the detailed content of Analysis of the gtime module of the GoFrame framework and custom time formatting syntax. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

PHPisstillrelevantinmodernenterpriseenvironments.1.ModernPHP(7.xand8.x)offersperformancegains,stricttyping,JITcompilation,andmodernsyntax,makingitsuitableforlarge-scaleapplications.2.PHPintegrateseffectivelyinhybridarchitectures,servingasanAPIgateway

Avoid N 1 query problems, reduce the number of database queries by loading associated data in advance; 2. Select only the required fields to avoid loading complete entities to save memory and bandwidth; 3. Use cache strategies reasonably, such as Doctrine's secondary cache or Redis cache high-frequency query results; 4. Optimize the entity life cycle and call clear() regularly to free up memory to prevent memory overflow; 5. Ensure that the database index exists and analyze the generated SQL statements to avoid inefficient queries; 6. Disable automatic change tracking in scenarios where changes are not required, and use arrays or lightweight modes to improve performance. Correct use of ORM requires combining SQL monitoring, caching, batch processing and appropriate optimization to ensure application performance while maintaining development efficiency.

To build a flexible PHP microservice, you need to use RabbitMQ to achieve asynchronous communication, 1. Decouple the service through message queues to avoid cascade failures; 2. Configure persistent queues, persistent messages, release confirmation and manual ACK to ensure reliability; 3. Use exponential backoff retry, TTL and dead letter queue security processing failures; 4. Use tools such as supervisord to protect consumer processes and enable heartbeat mechanisms to ensure service health; and ultimately realize the ability of the system to continuously operate in failures.

Using the correct PHP basic image and configuring a secure, performance-optimized Docker environment is the key to achieving production ready. 1. Select php:8.3-fpm-alpine as the basic image to reduce the attack surface and improve performance; 2. Disable dangerous functions through custom php.ini, turn off error display, and enable Opcache and JIT to enhance security and performance; 3. Use Nginx as the reverse proxy to restrict access to sensitive files and correctly forward PHP requests to PHP-FPM; 4. Use multi-stage optimization images to remove development dependencies, and set up non-root users to run containers; 5. Optional Supervisord to manage multiple processes such as cron; 6. Verify that no sensitive information leakage before deployment

PHP's garbage collection mechanism is based on reference counting, but circular references need to be processed by a periodic circular garbage collector; 1. Reference count releases memory immediately when there is no reference to the variable; 2. Reference reference causes memory to be unable to be automatically released, and it depends on GC to detect and clean it; 3. GC is triggered when the "possible root" zval reaches the threshold or manually calls gc_collect_cycles(); 4. Long-term running PHP applications should monitor gc_status() and call gc_collect_cycles() in time to avoid memory leakage; 5. Best practices include avoiding circular references, using gc_disable() to optimize performance key areas, and dereference objects through the ORM's clear() method.

ReadonlypropertiesinPHP8.2canonlybeassignedonceintheconstructororatdeclarationandcannotbemodifiedafterward,enforcingimmutabilityatthelanguagelevel.2.Toachievedeepimmutability,wrapmutabletypeslikearraysinArrayObjectorusecustomimmutablecollectionssucha

Bref enables PHP developers to build scalable, cost-effective applications without managing servers. 1.Bref brings PHP to AWSLambda by providing an optimized PHP runtime layer, supports PHP8.3 and other versions, and seamlessly integrates with frameworks such as Laravel and Symfony; 2. The deployment steps include: installing Bref using Composer, configuring serverless.yml to define functions and events, such as HTTP endpoints and Artisan commands; 3. Execute serverlessdeploy command to complete the deployment, automatically configure APIGateway and generate access URLs; 4. For Lambda restrictions, Bref provides solutions.

The settings.json file is located in the user-level or workspace-level path and is used to customize VSCode settings. 1. User-level path: Windows is C:\Users\\AppData\Roaming\Code\User\settings.json, macOS is /Users//Library/ApplicationSupport/Code/User/settings.json, Linux is /home//.config/Code/User/settings.json; 2. Workspace-level path: .vscode/settings in the project root directory
