Data designer DEFAULT CURRENT_TIMESTAMP problematic

  • Resolved kebhin

    (@kebhin)


    1 year, 9 months ago

    Hi

    I have been developing on 2 sites, one with tables created outside wpda and one more recently using Data Designer to update table structure. I have a field book_date defined as timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, but when this has been updated using data designer there seems to be a subtle difference in the table definition. As a result the form validation code is fooled and when I try to Add New I get ‘book_date’ must be entered (it is not recognising there is a default value)

    I will send you screenshots of the way it looks in each database from Data Explorer, and also the html extracts that show why in one case it recognises a value will be generated and in the other the code believes it is a blank field that needs to be entered – using your contact form

    Best regards

    Kebhin

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Kim L

    (@kimmyx)

    Hi Kebhin,

    We’ve received your message and responded there.

    We’ll wait for your response. ??

    Thread Starter kebhin

    (@kebhin)

    Hi Kim/Peter

    I appreciate your responses, I was able to get this working with the right combination of settings, and by reconciling the data designer with the table itself – the topic can be closed

    Thank you

    Kebhin

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Data designer DEFAULT CURRENT_TIMESTAMP problematic’ is closed to new replies.