"Malformed" data flagged, cannot save data.

[fedaykinofdune]

This is my first go round with a tool like this, so it is quite possible I'm experiencing an issue related to mis-configuration of my server. Anyway, I'm using this to keep an eye on my MPOS cryptocoin pools databases. In the "Shares" section, every user's share is logged with a timestamp, like so: Thu Jun 19 2014 20:04:31 GMT-0400 (EDT) It is flagging the timestamps as "Malformed" and won't allow me to save data in other fields as a result. Is there something I can set to have it ignore the malformed bits? I wonder if the timestamp problem is due to some mis-configuration on my end?

Very nice tool, by the way! Much more convenient and tons easier to use than mySQL Workbench or phpmyadmin and others! Thanks

[simov]

Hi, @fedaykinofdune

The problem is the validator makes certain assumptions about the timestamp format outlined here

I'm assuming you want to edit existing records, that have a timestamp field already set.

In this case a very quick and dirty fix will be to set the timestamp column type to varchar(255), as the text fields doesn't have any other validation except for their length, and leave the control type as text.

{
    "control": {
        "text": true
    },
    "type": "varchar(255)"
}

The value of the type key is related only to the validation process.

Let me know if this doesn't work, or if your configuration requires something else.

[fedaykinofdune]

Excellent, thanks for the explanation, I'm still familiarizing myself with mySQL so your tool really helps out with some constant headaches. Thanks for the workaround as well! Normally if I have to edit anything in my pool's database, I have to change a batch of share id's or something which can be done in one line but your tool is particularly useful for looking at and then manually flagging "strange" records for later comparison, so the workaround will definitely help!

On Fri, Jun 20, 2014 at 2:58 AM, simo notifications@github.com wrote:

Hi, @fedaykinofdune https://github.com/fedaykinofdune

The problem is the validator makes certain assumptions about the timestamp format outlined here http://dev.mysql.com/doc/refman/5.1/en/datetime.html

I'm assuming you want to edit existing records, that have a timestamp field already set.

In this case a very quick and dirty fix will be to set the timestamp column type to varchar(255), as the text fields doesn't have any other validation except for their length, and leave the control type as text.

{ "control": { "text": true }, "type": "varchar(255)"}

The value of the type key is related only to the validation process.

Let me know if this doesn't work, or if your configuration requires something else.

— Reply to this email directly or view it on GitHub https://github.com/simov/express-admin/issues/50#issuecomment-46653729.