Order of fields in ORDS is not the same as in the original Access databsae

google-code-export / ords

Automatically exported from code.google.com/p/ords

1 stars 0 forks source link

Order of fields in ORDS is not the same as in the original Access databsae #546

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Upload an Access database into ORDS
2. Notice that the order of fields in the schema designer and data editing view 
is not the same as in the original tables
3.

What is the expected output? What do you see instead?
Fields are being arranged alphabetically when uploaded into ORDS, but this 
often doesn't make any sense. They should instead be ordered as they were in 
the original Access file. This was working previously (it was only when the 
schema was altered and re-saved that the order of fields was being reversed). 
Could we revery whilst still avoiding the re-ordering if a schema was 
subsequently altered after upload?

Please use labels and text to provide additional information.
Dev 1.0.4 using Chrome

Original issue reported on code.google.com by jajwil...@gmail.com on 29 Sep 2014 at 1:13

GoogleCodeExporter commented 9 years ago

Original comment by jajwil...@gmail.com on 29 Sep 2014 at 1:29

Added labels: Milestone-1.0.6
Removed labels: 1.0.6

GoogleCodeExporter commented 9 years ago

Uh 'revery'='revert'. My mind was evidently elsewhere when I wrote that. But 
that doesn't solve the problem.

Original comment by jajwil...@gmail.com on 8 Oct 2014 at 2:24

GoogleCodeExporter commented 9 years ago

Original comment by jajwil...@gmail.com on 10 Dec 2014 at 4:35

Added labels: Milestone-1.0.7
Removed labels: Milestone-1.0.6

GoogleCodeExporter commented 9 years ago

Original comment by jajwil...@gmail.com on 16 Feb 2015 at 10:29

Added labels: Milestone-1.0.8
Removed labels: Milestone-1.0.7

GoogleCodeExporter commented 9 years ago

And this issue has also been raised by a user, so upping priority.

Original comment by jajwil...@gmail.com on 17 Feb 2015 at 11:13

Added labels: Priority-Critical
Removed labels: Priority-High

GoogleCodeExporter commented 9 years ago

Original comment by thest...@gmail.com on 23 Feb 2015 at 12:16

Changed state: Started

GoogleCodeExporter commented 9 years ago

Seems this has been fixed. I can only assume our recent user was referring to a 
database that had been uploaded several months before.

Original comment by jajwil...@gmail.com on 23 Feb 2015 at 2:26

Changed state: Fixed