Thread: Smallint
Am I missing something obvious, or is the SMALLINT datatype missing from the appliation (add column on Columns tab of database property sheet)? ahp
Duh! Obviously it's not, it's just that pgAdmin3 calls it an int2? Any reason not to call it a smallint, since that's they way it's referred to in the documentation? ahp
Adam H. Pendleton wrote: > Duh! Obviously it's not, it's just that pgAdmin3 calls it an int2? > Any reason not to call it a smallint, since that's they way it's > referred to in the documentation? Yeah. Virtually all types are read from the database. SMALLINT and INTEGER are parser translations, and there might be more. IMHO, the combobox already shows way to much. Only types that don't have a pg_type entry (serial, bigserial) are added manually. Regards, Andreas
Adam H. Pendleton wrote: > Am I missing something obvious, or is the SMALLINT datatype missing > from the appliation (add column on Columns tab of database property > sheet)? Just try int2... Regards, Andreas
Hi! What do I need to do to volunteer as a translator? I'm interested in translating pgAdmin3 into Slovenian language. -- Lp, Miha
> -----Original Message----- > From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] > Sent: 18 August 2003 18:41 > To: Adam H. Pendleton > Cc: pgadmin-hackers > Subject: Re: [pgadmin-hackers] Smallint > > > Adam H. Pendleton wrote: > > > Duh! Obviously it's not, it's just that pgAdmin3 calls it an int2? > > Any reason not to call it a smallint, since that's they way it's > > referred to in the documentation? > > Yeah. > Virtually all types are read from the database. SMALLINT and > INTEGER are > parser translations, and there might be more. IMHO, the > combobox already > shows way to much. > > Only types that don't have a pg_type entry (serial, > bigserial) are added > manually. For v2, perhaps we should default to an 'newbie mode' (obviously not called that ;-) ) in which we list only the standard SQL types and their array equivalents? I have seen datatype queries from newbies a number of times in the past. Regards, Dave
> What do I need to do to volunteer as a translator? I'm interested in > translating pgAdmin3 into Slovenian language. Dear Miha, Sorry for the delay. I needed some time to update pgAdmin3 web site in order to display the translation howto. The translation page is available from http://snake.pgadmin.org/pgadmin3/translation.php#howto. Upon reception of your language names, we will update pgAdmin3 and the website. Please note that you can start translating right now downloading pgAdmin3.pot file. Just for information, does Slovenian differ a lot from Croatian which we already support? What is the origin of the Slovenian language? Cheers, Jean-Michel
Hi! Send us the English and translated names of your language: "French" and "Français", "German" and "Deutsch", etc.. This will allow us to modify pgAdmin src/ui/pgadmin3.lng file to display the language name in pgAdmin. We will also create a directory according to your locale canonical name under /usr/share/pgadmin3/ui (GNU/Linux and other Unixes) or c:\program files\pgadmi3\ui (Win32). The list of language codes can be found on <http://www.debian.org/international/l10n/po>Debian site. English name: Slovenian Original (translated) name: Slovenèina ( == s with hachek, è == c with hachek) Language code: sl_SI Slovenian is in some ways similar to Croatian, they are both Slavic by origin, but it is quite different nevertheless. It is also one of the few languages which also has, besides singular and plural, dual. So it can be a bit tricky to translate from time to time. At 11:45 19.8.2003 +0200, Jean-Michel POURE wrote: >Sorry for the delay. I needed some time to update pgAdmin3 web site in order >to display the translation howto. The translation page is available from >http://snake.pgadmin.org/pgadmin3/translation.php#howto. > >Upon reception of your language names, we will update pgAdmin3 and the >website. Please note that you can start translating right now downloading >pgAdmin3.pot file. > >Just for information, does Slovenian differ a lot from Croatian which we >already support? What is the origin of the Slovenian language? -- Lp, Miha
Miha Radej wrote: > > English name: Slovenian > Original (translated) name: Slovenšèina (š == s with hachek, è == c > with hachek) > Language code: sl_SI Hi Miha, you have been added to the translator's pages, welcome! You may send the created *.mo file Jean-Michel or me, to get it added/updated to the project. Regards, Andreas
Dave Page wrote: >For v2, perhaps we should default to an 'newbie mode' (obviously not >called that ;-) ) in which we list only the standard SQL types and their >array equivalents? I have seen datatype queries from newbies a number of >times in the past. > I'm thinking of a reduced mode, offering only "common" types. Does the average pgsql user use regoperator[] very often ? ;-) IMHO, the combobox is too full, I'd need only a few basic types and my domains. Regards, Andreas
On Thursday, Aug 21, 2003, at 05:54 US/Eastern, Andreas Pflug wrote: > I'm thinking of a reduced mode, offering only "common" types. Does the > average pgsql user use regoperator[] very often ? ;-) > IMHO, the combobox is too full, I'd need only a few basic types and my > domains. > I completely agree, assuming, of course, that for users that do want to use regoperator[], they still can, without having to resort to the SQL dialog. Perhaps an option "Use advanced data types" or something like that could change the combo box's contents. ahp