1) Do you want to be able to do this action (change physical order of fields in table)
a) on the step of dB Design? >> At DB Design Time as I frequently am adding, deleting or inserting new fields into a table as I work through the initial DB Schema
b) or when db exists on disk already? >> It would be nice to be able to do this operation on an active DB >> perhaps an operator could select the columns through a wizard that merely runs an SQL script.
If we talk mainly about 1a case, then the best step I think is to use our Diagrams. Although we need to add change order of fields to diagrams also, this is easy enough step.
Change physical order of fields in an existed table with records, is a more hard task which takes longer time. And for each DB it takes own efforts.
2) Are you going to use this SQLite DB later from some app code OR you going to use Vstudio itself?
In the second case - Layout can have any order.
1) Do you want to be able to do this action (change physical order of fields in table)
a) on the step of dB Design?
b) or when db exists on disk already?
If we talk mainly about 1a case, then the best step I think is to use our Diagrams. Although we need to add change order of fields to diagrams also, this is easy enough step.
Change physical order of fields in an existed table with records, is a more hard task which takes longer time. And for each DB it takes own efforts.
2) Are you going to use this SQLite DB later from some app code OR you going to use Vstudio itself?
In the second case - Layout can have any order.
There are no replies made for this post yet. However, you are not allowed to reply to this post.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »