Thread:
BiggerSQL-1.2.4 was released recently BiggerSQL is a Cocoa based Postgresql browser for Mac OS X. This release fixes a couple of bugs and adds a couple on new features. From the Version History document: Jun 12, 2004 Version 1.2.4 released. I cleaned up a big memory leak in the outline view window. A bug in the relogin procedure that caused the script menu to be improperly rebuild was fixed. The File menu has a new item "Visually Display NULL fields". When checked, "<NULL>" is displayed in every field that is null in the results window, when unchecked the field is filled with the empty string. There are several changes with the Scripts menu. The Script menu will now will construct submenus matching the directory structure of the Script Folder. When an item is selected from the Scripts menu, the path name of the script will be inserted at the top of the editor panel as a sql comment. The Script menu now has an item "Update Script Menu". When selected, this item will cause the Script menu to be rebuilt. Execution time in milliseconds is now displayed in the Status window. Clicking on a field name in the info drawer will now transfer the name to the edit window. BiggerSQL can be found at http://homepage.mac.com/levanj/Cocoa Enjoy Jerry
fotoinfo
Beatiful work! I'm already using it instead of the similar <italic>Postman Query</italic> program. d. On 13. jul 2004, at 20:13, Jerry LeVan wrote: <excerpt>BiggerSQL-1.2.4 was released recently BiggerSQL is a Cocoa based Postgresql browser for Mac OS X. This release fixes a couple of bugs and adds a couple on new features. From the Version History document: Jun 12, 2004 Version 1.2.4 released. I cleaned up a big memory leak in the outline view window. A bug in the relogin procedure that caused the script menu to be improperly rebuild was fixed. The File menu has a new item "Visually Display NULL fields". When checked, "<<NULL>" is displayed in every field that is null in the results window, when unchecked the field is filled with the empty string. There are several changes with the Scripts menu. The Script menu will now will construct submenus matching the directory structure of the Script Folder. When an item is selected from the Scripts menu, the path name of the script will be inserted at the top of the editor panel as a sql comment. The Script menu now has an item "Update Script Menu". When selected, this item will cause the Script menu to be rebuilt. Execution time in milliseconds is now displayed in the Status window. Clicking on a field name in the info drawer will now transfer the name to the edit window. BiggerSQL can be found at http://homepage.mac.com/levanj/Cocoa Enjoy Jerry ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster </excerpt> Beatiful work! I'm already using it instead of the similar Postman Query program. d. On 13. jul 2004, at 20:13, Jerry LeVan wrote: > BiggerSQL-1.2.4 was released recently BiggerSQL is a Cocoa based > Postgresql browser > for Mac OS X. > > This release fixes a couple of bugs and adds a couple on new features. > > From the Version History document: > > Jun 12, 2004 Version 1.2.4 released. I cleaned up a big memory leak in > the outline view window. A bug in the relogin procedure that caused the > script menu to be improperly rebuild was fixed. The File menu has a new > item "Visually Display NULL fields". When checked, "<NULL>" is > displayed > in every field that is null in the results window, when unchecked the > field is filled with the empty string. There are several changes with > the Scripts menu. The Script menu will now will construct submenus > matching the directory structure of the Script Folder. When an item is > selected from the Scripts menu, the path name of the script will be > inserted at the top of the editor panel as a sql comment. The Script > menu now has an item "Update Script Menu". When selected, this item > will > cause the Script menu to be rebuilt. Execution time in milliseconds is > now displayed in the Status window. Clicking on a field name in the > info > drawer will now transfer the name to the edit window. > > BiggerSQL can be found at http://homepage.mac.com/levanj/Cocoa > > Enjoy > > Jerry > > > ---------------------------(end of > broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >
>Screen and Music
Screen
Lovely animals<br /><br /><br />
> could phppgadmin serve your purpose? > http://phppgadmin.sourceforge.net/ Not exactly... I am looking for a more customized ways to present a user an option to edit the data. For example, a user will click an edit link on a certain item (from the main interface) and he'll be presented with a form that allows him easily to edit this specific items. Notice, that the user won't see the regular column names or IDs as he would with any raw database admin system, instead, he'd see the softer version with easy field names and where IDs are automatically formed into listboxes. I found several systems that get close to the idea, but none is exactly what I'm looking for: DBForm (http://dbform.sourceforge.net/): Seems quite good, if I will be able to grasp all its functions as its original form is not exactly what I need. NetXTensio (http://www.interaktonline.com/Products/Dreamweaver-Extensions/NeXTensio/Overview/) - It is a dreamweaver extension... Besides being expensive I couldn't to get it work properly with PostgreSQL :(. If someone has another ideas I'd be glad to hear. ------------------------------------------------------------------------------------------------ Laser wrote: > could phppgadmin serve your purpose? > http://phppgadmin.sourceforge.net/ Vitaly wrote: > I'm looking for software that can generate PHP scripts from PostgreSQL > database that will allow for distant users to edit the data. > > The idea is to let selected users have EASY access to edit the data > they see, I can't possibly give raw access with pgMyAdmin or anything > of sorts, as it is hardly accessible for the average user. > > For MySQL I know the PHPMaker (http://www.hkvstore.com/phpmaker/) but > I haven't yet found anything of sorts for PostgreSQL. > > Needed features: > > * Ability to add/edit/delete data. > * Ability to mask the columns and show only some of them (for example, > the numerical pk is not needed). > * Ability to work with joins between tables (e.g customer and > customer_type, which means the customer will have a column with a list > box letting the user choose the type). > * Would be really nice if it had some kind of option to save the > changed but not to apply them until someone approves them... > > Anyone knows some kind of software that does that? -- ICQ: 1912453 AIM: VitalyB1984 MSN: tmdagent@hotmail.com Yahoo!: VitalyBe
Thanks for your answer! I would like to kill only a postgres session not postmaster. The table pg_session indicates the pid of the wrong session but kill -INT <pid> didn't stop this session. pg_ctl works fine when i want to stop postmaster with the argument '-m immediate stop' ----Message d'origine---- >Date: Wed, 27 Oct 2004 10:11:16 +0100 >De: Richard Huxton <dev@archonet.com> >A: f-f@club-internet.fr >Copie à: pgsql-general@postgresql.org >Sujet: Re: [GENERAL] > >f-f@club-internet.fr wrote: >> Hello ! >> >> To kill a session i used KILL -INT <PID>. >> >> This command wasn't successfull. The processus is still here when a >> 'ps ax' or a 'select * from pg_stat_activity' >> >> Is there an other way to kill this process only because a web server >> 24/7 use postgres and cannot stop postgresql now. > > From the manuals: >To terminate the postmaster normally, the signals SIGTERM, SIGINT, or >SIGQUIT can be used. The first will wait for all clients to terminate >before quitting, the second will forcefully disconnect all clients, and >the third will quit immediately without proper shutdown, resulting in a >recovery run during restart. > >The utility command pg_ctl can be used to start and shut down the >postmaster safely and comfortably. > >Does pg_ctl do anything for you? > >-- > Richard Huxton > Archonet Ltd > >---------------------------(end of broadcast)--------------------------- >TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > >