var_dump(new DateTimeImmutable('yesterday'));
//object(DateTimeImmutable)#1 (3) {
// ["date"]=> string(26) "2023-05-03 00:00:00.000000"
// ["timezone_type"]=> int(3)
// ["timezone"]=> string(3) "UTC"
//}
var_dump(new DateTimeImmutable('1 day ago'));
//object(DateTimeImmutable)#1 (3) {
// ["date"]=> string(26) "2023-05-03 05:14:22.254741"
// ["timezone_type"]=> int(3)
// ["timezone"]=> string(3) "UTC"
//}
PayPal-Request-Id : Optional. Contains a unique user-generated ID that the server stores for a period of time. Use this header to enforce idempotency on REST API POST calls. You can make these calls any number of times without concern that the server creates or completes an action on a resource more than once. You can retry calls that fail with network timeouts or the HTTP 500 status code. You can retry calls for as long as the server stores the ID.
For example, a user calls refund captured payment with the PayPal-Request-Id header that contains a unique user-provided ID. The user can make the call again with the same ID in the PayPal-Request-Id header for up to 45 days because the server stores this ID for this long for this call.
If the initial call fails with the HTTP 500 status code but the server has already refunded the payment, the caller does not need to worry that the server will refund the payment again.
ldap_set_option(LDAP_OPT_PROTOCOL_VERSION, 3);
(&(&(objectClass=user)(objectCategory=PERSON))(|(memberof=CN=Access-VPN-BitrixVM,OU=VPN,OU=Access,OU=Groups,OU=CO,DC=company,DC=local)(memberof=CN=Отдел клиентского сервиса \(Call-центр\),OU=Depart,OU=Groups,OU=CO,DC=company,DC=local)))
grep -r '$siteLanguage' /site/root/*
chat_id - This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.То есть, для хранения chat_id надо использовать 64-битные значения. Для MySQL, например, это тип BIGINT.