View contents is exported as table data (with "insert into " sql command). When importing, it of course fails with an error, because the view is of course not updatable.
Ok, I would say that it's the user's responsability to untick the Data checkbox in this case. There are cases where we have to export data for a VIEW, for example when generating a PDF export.
Comments?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) "... this happens only when exporting a single view ..."
No - for me it exports data from view even if you export whole database. (I have version 2.9.2 on webhosting, can't try newer unfortunatelly).
2) "Ok, I would say that it's the user's responsability to untick the Data
checkbox in this case. There are cases where we have to export data for a
VIEW, for example when generating a PDF export."
I think it SHOULDN'T export data in SQL export, because it doesn't make sense and data will NOT be accepted by import.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=210714
Originator: NO
Note: this happens only when exporting a single view. Exporting the full database does not generate INSERTs for VIEWs.
Logged In: YES
user_id=210714
Originator: NO
Ok, I would say that it's the user's responsability to untick the Data checkbox in this case. There are cases where we have to export data for a VIEW, for example when generating a PDF export.
Comments?
Logged In: YES
user_id=1841109
Originator: YES
1) "... this happens only when exporting a single view ..."
No - for me it exports data from view even if you export whole database. (I have version 2.9.2 on webhosting, can't try newer unfortunatelly).
2) "Ok, I would say that it's the user's responsability to untick the Data
checkbox in this case. There are cases where we have to export data for a
VIEW, for example when generating a PDF export."
I think it SHOULDN'T export data in SQL export, because it doesn't make sense and data will NOT be accepted by import.
works for me under 2.9.2.
Logged In: YES
user_id=210714
Originator: NO
1. I cannot reproduce this problem under 2.9.2. I attached my example here.
Please attach here a small example to help me reproduce this.
File Added: base2_autre.sql
Logged In: YES
user_id=210714
Originator: NO
2. Fixed in 2.11-dev.