Thread: [SQLObject] Column creation order
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: David D. <cou...@gm...> - 2005-03-30 04:53:47
|
Is there a method to the order that the columns are created in. I have a situation where I have a base class, and extension then the actual table that I use and there seems to be no reason to hoy the fields are ordered. For instance I get country, addr4, addr5, addr3, addr2, addr1, postalcode, finally state. This is when I defined a1, 2,3,4,5 city start postalcode, country. Is there a way to coerse the order? If I only ever use the tables with sqlobject this isn't a problem, but eventually we will have to show the tables to some one. What would be ideal would be the pk followed by all of the fields in alpha order. -- *********************************** See there, that wasn't so bad. *********************************** |
From: Ahmed M. A. <ahm...@wa...> - 2005-03-31 11:04:09
|
Hi all, Is there a way to use unicode with sqlobject ? I am working on unicode aware database (postgresql 8 ). Thanks Ahmed MOHAMED ALI |
From: Ian B. <ia...@co...> - 2005-03-31 20:41:33
|
David Driver wrote: > Is there a method to the order that the columns are created in. I have > a situation where I have a base class, and extension then the actual > table that I use and there seems to be no reason to hoy the fields are > ordered. For instance I get country, addr4, addr5, addr3, addr2, > addr1, postalcode, finally state. This is when I defined a1, 2,3,4,5 > city start postalcode, country. > > Is there a way to coerse the order? If I only ever use the tables with > sqlobject this isn't a problem, but eventually we will have to show > the tables to some one. What would be ideal would be the pk followed > by all of the fields in alpha order. Not now. There will be -- we'll track the chronological order in which you instantiated the *Col objects, and use that to sort the fields. -- Ian Bicking / ia...@co... / http://blog.ianbicking.org |
From: Andy T. <an...@gm...> - 2005-04-01 00:55:47
|
On Thu, 31 Mar 2005 14:39:40 -0600, Ian Bicking <ia...@co...> wrote: > David Driver wrote: > > Is there a method to the order that the columns are created in. I have > > a situation where I have a base class, and extension then the actual > > table that I use and there seems to be no reason to hoy the fields are > > ordered. For instance I get country, addr4, addr5, addr3, addr2, > > addr1, postalcode, finally state. This is when I defined a1, 2,3,4,5 > > city start postalcode, country. > > > > Is there a way to coerse the order? If I only ever use the tables with > > sqlobject this isn't a problem, but eventually we will have to show > > the tables to some one. What would be ideal would be the pk followed > > by all of the fields in alpha order. > > Not now. There will be -- we'll track the chronological order in which > you instantiated the *Col objects, and use that to sort the fields. > > -- > Ian Bicking / ia...@co... / http://blog.ianbicking.org > > Would it not be better to have an explicit (optional) order attribute for the column? That way the storage order of the columns can be defined by the developer. Of course, this is only a problem if you use SQLObject to create your tables. As far as normal SQL operations are concerned column order is irrelevant. A workaround would be to create the tables yourself in your database and then the columns can be in whatever order you like. Regards, Andy -- From the desk of Andrew J Todd esq |
From: Carlos R. <car...@gm...> - 2005-04-01 02:01:06
|
On Fri, 1 Apr 2005 10:55:36 +1000, Andy Todd <an...@gm...> wrote: > On Thu, 31 Mar 2005 14:39:40 -0600, Ian Bicking <ia...@co...> wrote: > > David Driver wrote: > > > Is there a method to the order that the columns are created in. I have > > > a situation where I have a base class, and extension then the actual > > > table that I use and there seems to be no reason to hoy the fields are > > > ordered. For instance I get country, addr4, addr5, addr3, addr2, > > > addr1, postalcode, finally state. This is when I defined a1, 2,3,4,5 > > > city start postalcode, country. > > > > > > Is there a way to coerse the order? If I only ever use the tables with > > > sqlobject this isn't a problem, but eventually we will have to show > > > the tables to some one. What would be ideal would be the pk followed > > > by all of the fields in alpha order. > > > > Not now. There will be -- we'll track the chronological order in which > > you instantiated the *Col objects, and use that to sort the fields. > > > > -- > > Ian Bicking / ia...@co... / http://blog.ianbicking.org > > > > > > Would it not be better to have an explicit (optional) order attribute > for the column? That way the storage order of the columns can be > defined by the developer. Why have an extra argument? The order of creation *is* defined by the developer, although implicitly, by the order the columns are declared in the class statement. There are a few ways to solve this problem, and in fact, this has already been discussed before. It's not hard to do, and I assume that it was not done before mostly because it was not a priority. > Of course, this is only a problem if you use SQLObject to create your > tables. As far as normal SQL operations are concerned column order is > irrelevant. It is slighly relevant, or at least convenient... specially when reading the results of a select directly, or when using simple consolve based, text-only administrative tools. It's also useful for introspection, for automatic tools such as report & form generators, so they can generate a reasonable representation of the data without too much input from the developer (think about a Rails-like environment, and you will understand what I mean). -- Carlos Ribeiro Consultoria em Projetos blog: http://rascunhosrotos.blogspot.com blog: http://pythonnotes.blogspot.com mail: car...@gm... mail: car...@ya... |