Page 1 of 1
Make CSV in 1.36 suitable for 1.37?
Posted: Thu Feb 01, 2024 10:59 am
by dougmccrary
I can make it, but without field names, so does not import correctly...is it doable?
If so, clues?
Thanks.
Re: Make CSV in 1.36 suitable for 1.37?
Posted: Thu Feb 01, 2024 1:58 pm
by iconnor
What are we talking about here? CSV of what?
The only csv I can think of is the events list which isn't importable...
Re: Make CSV in 1.36 suitable for 1.37?
Posted: Fri Feb 02, 2024 2:04 am
by dougmccrary
Sorry. Monitors
No zones.
Suitable for the 1.37 import function, if it's working.
Re: Make CSV in 1.36 suitable for 1.37?
Posted: Fri Feb 02, 2024 2:39 pm
by iconnor
Are you referring to the import on the add_monitors view?
I'm really confused. What are you using to do the export/import? I'm not aware of this existing. Is it something you've written?
I don't think I've changed any fields other than Function and Enabled. But the columns are still there, so an sql dump/restore should still work.
Re: Make CSV in 1.36 suitable for 1.37?
Posted: Sat Feb 03, 2024 2:18 am
by dougmccrary
Are you referring to the import on the add_monitors view?
Right.
export from 1.36:
mysqldump -h localhost -u root --tab=. zm Monitors > Monitors.txt
import add_monitors csv
It created the monitors, but the fields were wrong. Then I noticed the fields were not specified in the 1.36 csv.
I don't think I've changed any fields other than Function and Enabled. But the columns are still there, so an sql dump/restore should still work.
Yeah, sorry to bother about it - I just somehow had not noticed the csv thing, so wanted to try it.
Re: Make CSV in 1.36 suitable for 1.37?
Posted: Sat Feb 03, 2024 7:25 pm
by iconnor
That import was something quickly convoluted together for tesla not as a complete db dump... I thought the fields were specified in the import pop-up so youd have to make sure it matched. Def needs work