Invalid SQL: REPLACE INTO `swsessions` (`sessionid`, `ipaddress`, `lastactivity`, `useragent`, `isloggedin`, `sessiontype`, `typeid`, `dateline`, `status`) VALUES('3efg7bteca4obbvn2qj5qbxnke5v8bzk', '216.73.216.213', '1751421229', 'Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatibl', '0', '40', '0', '1751421229', '0'); (The table 'swsessions' is full) Nanacast API: Using u_username vs. u_email - Powered By Kayako eSupport
01 Jul 2025 
Support Center » Knowledgebase » Technical FAQs » Nanacast API: Using u_username vs. u_email
 Nanacast API: Using u_username vs. u_email
Solution

u_username is for cases where you want to allow people to create their own username, instead of having their email address be the username, which is the default. Also, u_username has a built-in feature where there system will automatically check for and prevent duplicates. u_email can prevent duplicates as well, but that is off by default. You need to checkmark to enable it under Custom Fields/Notifications > Edit Email.





Keywords: API, username, user email



Article Details
Article ID: 75
Created On: 24 Mar 2010 02:58 PM

 This answer was helpful  This answer was not helpful

 Back
 Login [Lost Password] 
Email:
Password:
Remember Me:
 
 Search
 Article Options
Home | Register | Submit a Ticket | Knowledgebase | News
Language:

Help Desk Software By Kayako eSupport v3.60.04