Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

storing IDN in database

DonkeyDonkey Member

what is correct form of email address, domain to store in database like mysql, mariadb that has idn.
example: смегма.рф or xn--80aff1ac0a.xn--p1ai

Comments

  • jarjar Patron Provider, Top Host, Veteran

    Suppose you could store it any way you like, the real meat of it is whether or not you can quickly make use of the way you've stored it with the application querying the database.

    Thanked by 1cadddr
  • LeviLevi Member

    Do not encode idn. Save in raw format (text). This way you will have maximum flexibility to manipulate data.

  • @jar said: Suppose you could store it any way you like, the real meat of it is whether or not you can quickly make use of the way you've stored it with the application querying the database.

    In other words, normalize everything to either IDN or Punycode. My preference would be to have everything in Punycode, that way a wrong collation on MySQL doesn't end up mangling the data in your database.

    Thanked by 3szymonp jar scooke
Sign In or Register to comment.