Dave Page a écrit : > Guillaume Lelarge wrote: >> Dave Page a écrit : >>> [...] >>> I'm currently thinking the way forward is to do the following: >>> >>> - Allow the user to create shell types. This would be another option >>> alongside Composite, Enumeration and External. >>> >>> - Populate the combo boxes for the aforementioned functions when the >>> user changes to the tab they're on, using the type name entered on the >>> first tab to select the appropriate functions. >>> >> Your first idea seems much more simple to code than the second one but >> it's more work for the user... but, as you say, no one sent report on >> this issue, so I'm all for the first idea. > > Those two are individual parts of the same idea. We'd need to do both :-( >
Oops. I didn't understand this. This probably means I should go to bed earlier :) > Idea number one is the more complex one in which the user can create the > required functions as part of the process of creating the type - ie. we > spawn sub-dialogues in which the functions can be defined as required. > I need to take a better look at this. I know the contents of second tab depend on which kind of type we want to create, but I thought it was easy to do. Sorry about this... -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
