@billinkc That looks interesting and I might need to see how easily it would be to get my template from Visio in there.

at one point, there was a .net library that allowed you to write the xml that powers a diagram so you could systematically build diagrams from metadata

Morning

Good morning

Morning

Morning

Morning

Morning

thunder map today: meteo.gr/thunders.cfm

@ypercubeᵀᴹ I get a popup frame with two buttons. What does each of them say?

blue, on the right, is accept all

Thanks, I pressed that one, doesn't matter much in Private Mode after all.

@ypercubeᵀᴹ "Why is nothing happening" everything happens at once "Oh damn"

Google translate:

😀

heh, the wind map is cool: meteo.gr/anemologio.cfm

that's pretty

Ah, it looks like the caption of the button I clicked expressed my sentiment exactly

I really didn't know

I think I trust the ypercube translation a bit more than googly

haha, only now I read the I DON'T KNOW...

total failure of google translate

I thought it was funny

Seems like every pop up should have that option

I DON'T KNOW

ΕΝ ΟΙΔΑ ΟΤΙ ΟΥΔΕΝ ΟΙΔΑ

Structurally, that kind of resembles "to be or not to be", but I'm too lazy (or too distrusting? I Don't Know™!) to check that on Google Translate.

I know only one thing, that I know nothing.

@MichaelGreen thanks, more food for thought

Is there an elegant way to manage not knowing before hand what data type a MySQL field needs to be? Users can create their own form fields with e.g. float input, text input, int input, so as the form on a user account is not built with the DB tables I can't know the data type before hand.

I've read ideas such as: (1) Store everything as varchar; (2) Use Json; Neither of which take my fancy. I had the idea of separate tables for data types, so tbl_int, tbl_string, tbl_float (etc, and not those names) then the main table would store a mapping ID which would map to a specific table. Or fields with the types instead of tables such as field_int, field_float, etc and just store the value in the right field. Both of these seem rough too

@James There may be some useful info in this answer, which shows how to create a flexible schema using metadata, but is still hardened and easy to access through SQL statements: stackoverflow.com/a/4359193/13942986

Diagram is the most useful for me: softwaregems.com.au/Documents/Article/Sixth%20Normal%20Form/…

> he fired me and I started laughing

nice one