Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

MySQL text column error 1366

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    MySQL text column error 1366

    My application users are on rare occasion getting the "1366" error below when submitting records, with slight differences in the "\xE2\x98\x85" part. The column AMC_Comment2 is a MySQL longtext data type, and the Alpha Five control is a standard TextArea control (not HTML). That said, I'm aware of the same error coming from a text data type column with an HTML-formatted TextArea control as well.

    I have reason to believe it's related to text that's copied from some other source and pasted in, but presumably when it gets pasted, the formatting in the non-HTML TextArea control is removed prior to the record being submitted (is that true?). It's infrequent and so far un-replicate-able enough that I can't put a finger on the cause. Anyone have any ideas?

    Thanks in advance...

    Record was not updated. Less...
    Database API specific error

    Your database has returned the following error code and description to Alpha Five.
    Consult your database documentation for further information.

    1366 - 'Incorrect string value: '\xE2\x98\x85 Ch...' for column 'AMC_Comment2' at row 1'

    #2
    Re: MySQL text column error 1366

    Originally posted by christappan View Post
    My application users are on rare occasion getting the "1366" error below when submitting records, with slight differences in the "\xE2\x98\x85" part. The column AMC_Comment2 is a MySQL longtext data type, and the Alpha Five control is a standard TextArea control (not HTML). That said, I'm aware of the same error coming from a text data type column with an HTML-formatted TextArea control as well.

    I have reason to believe it's related to text that's copied from some other source and pasted in, but presumably when it gets pasted, the formatting in the non-HTML TextArea control is removed prior to the record being submitted (is that true?). It's infrequent and so far un-replicate-able enough that I can't put a finger on the cause. Anyone have any ideas?

    Thanks in advance...

    Record was not updated. Less...
    Database API specific error

    Your database has returned the following error code and description to Alpha Five.
    Consult your database documentation for further information.

    1366 - 'Incorrect string value: '\xE2\x98\x85 Ch...' for column 'AMC_Comment2' at row 1'
    Check your character encoding. Looks like you may be submitting data in one character encoding (like Latin-1) to the database that is using a different character encoding (such as UTF8). Here are links to others who had similar problems:

    http://www.webyog.com/forums/index.php?showtopic=6088
    http://forums.mysql.com/read.php?103...054#msg-419054
    http://www.dbforums.com/mysql/166332...ing-value.html

    Good luck.
    ---
    Sarah
    Alpha Anywhere latest pre-release

    Comment


      #3
      Re: MySQL text column error 1366

      Thanks--that's a good lead for sure and is probably the root. But this is just being submitted through the Alpha Five grid component submission, so I don't know how to know what encoding Alpha Five is using. I don't see anything in the XBasic at the component level or the control level that seems to specify... Any ideas?

      Comment


        #4
        Re: MySQL text column error 1366

        Originally posted by christappan View Post
        Thanks--that's a good lead for sure and is probably the root. But this is just being submitted through the Alpha Five grid component submission, so I don't know how to know what encoding Alpha Five is using. I don't see anything in the XBasic at the component level or the control level that seems to specify... Any ideas?
        A5 uses UTF-8.

        http://wiki.alphasoftware.com/Grid+C...aracters+V10.5
        http://wiki.alphasoftware.com/Workin...UTF-8+Data+V10

        Here's the unicode character in question, supposedly:
        ★ ---> \xe2\x98\x85

        What does your DB require/support?
        ---
        Sarah
        Alpha Anywhere latest pre-release

        Comment


          #5
          Re: MySQL text column error 1366

          This was tremendously helpful, and appears I could have gotten there myself if I'd googled it but your help significantly quickened the process. We were on latin1 encoding, the default for MySQL, but it's been changed now.

          Thanks again.

          Comment


            #6
            Re: MySQL text column error 1366

            Originally posted by christappan View Post
            This was tremendously helpful, and appears I could have gotten there myself if I'd googled it but your help significantly quickened the process. We were on latin1 encoding, the default for MySQL, but it's been changed now.

            Thanks again.
            Yeah. You probably could have found the answer a lot faster --- and probably would have never posted a question in the forums --- if you'd Googled your SQL error and then subsequently googled for Alpha's default character encoding. But if you'd done that, I wouldn't have gotten to answer a forum question! I like to help people solve problems. And my experience with Alpha is... severely limited. So really I only get to answer the "easy" questions. :P

            Plus, now there is a thread addressing "incorrect string values". That's bound to help out the next person who has this problem and comes to the A5 forums first. And I learned something. :)
            Alpha Anywhere latest pre-release

            Comment

            Working...
            X