Menu
▾
▴
sql-ledger-users
|
From: Thomas S. <ps...@on...> - 2001-02-15 22:18:49
|
As the postgres user, run "psql". At the psql prompt type \h to see help.
type \h {command_name} to get more specific help.
--
Thomas Sawyer
ps...@on... - email
(303) 285-3487 x1594 - voicemail/fax
---- Hal Davison <ha...@fa...> wrote:
>
> If there is a column that one creates by mistake, what is the PostgeSQL
> function/command that is used to DROP the COLUNM?
>
>
> --Hal.
> ===========================================================
> Hal Davison Internet Petroleum Gateway
> Davison Consulting Caldera 2.2.14 eServer
> 6850 Myakka Valley Tr PostgreSQL 7.03 - Sun Forte - JAVA
> Sarasota, Florida 34241 Phone: (941) 921-6578
> http://faams.net eFAX: (419) 821-5999
> ===========================================================
>
>
__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com
|
|
From: Thomas S. <ps...@on...> - 2001-02-15 23:45:56
|
Nice!
That's right, I remember now...Postgresql doesn't have a simple means
for dropping columns. I think you did the only thing you could do. This
transfers your data I take it? Hopefully this will be simplified in future
versions of Postgresql. By the way, what are you working on?
--
Thomas Sawyer
ps...@on... - email
(303) 285-3487 x1594 - voicemail/fax
---- "Pati Davison" <pa...@se...> wrote:
> Well Tom,
>
> Answer ain't there..but..did find:
>
> SELECT (..All columns except the one that you drop...)
> INTO TABLE tmp_name
> FROM old_table;
> DROP TABLE old_table;
> ALTER TABLE tmp_table RENAME TO old_table;
>
> This will do the trick..!!
>
>
>
> ----- Original Message -----
> From: Thomas Sawyer <ps...@on...>
> To: <sql...@li...>
> Sent: Thursday, February 15, 2001 5:19 PM
> Subject: Re: [SQL-Ledger-users] Drop Column?
>
>
> | As the postgres user, run "psql". At the psql prompt type \h to see
> help.
> | type \h {command_name} to get more specific help.
> |
> | --
> | Thomas Sawyer
> | ps...@on... - email
> | (303) 285-3487 x1594 - voicemail/fax
> |
> |
> |
> | ---- Hal Davison <ha...@fa...> wrote:
> | >
> | > If there is a column that one creates by mistake, what is the PostgeSQL
> | > function/command that is used to DROP the COLUNM?
> | >
> | >
> | > --Hal.
> | > ===========================================================
> | > Hal Davison Internet Petroleum Gateway
> | > Davison Consulting Caldera 2.2.14 eServer
> | > 6850 Myakka Valley Tr PostgreSQL 7.03 - Sun Forte - JAVA
> | > Sarasota, Florida 34241 Phone: (941) 921-6578
> | > http://faams.net eFAX: (419) 821-5999
> | > ===========================================================
> | >
> | >
> |
> | __________________________________________________
> | FREE voicemail, email, and fax...all in one place.
> | Sign Up Now! http://www.onebox.com
> |
>
>
>
__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com
|
|
From: Hal D. <ha...@fa...> - 2001-02-16 00:07:44
|
On Thu, 15 Feb 2001, you wrote: > Nice! > > That's right, I remember now...Postgresql doesn't have a simple means > for dropping columns. I think you did the only thing you could do. This > transfers your data I take it? Hopefully this will be simplified in future > versions of Postgresql. By the way, what are you working on? > Well, I have a current product done in the Progress 4GL product(NON-SQL) with the servers running Caldera 2.3(2.2.14) boxes. Clients connect from Win95/98 boxes by TCP/IP and NetTerm over 100BaseT networks. The product is designed for petroleum and lubricant distribution jobbers including a 'BackOffice' package for their C-Stores. I has all of the accounting packages including multi-state US payrolls. This market is odd in that all unit pricing is done to 5 decimal places. On any particular invoice there could be as many as 11 different taxes that might have to be computed, added and displayed individually. Moving to PostgreSQL so that we can use the various SQL report writers and the GUI garbage that the users think they want. Sorry for the long reply..:( --Hal. =========================================================== Hal Davison Internet Petroleum Gateway Davison Consulting Caldera 2.2.14 eServer 6850 Myakka Valley Tr PostgreSQL 7.03 - Sun Forte - JAVA Sarasota, Florida 34241 Phone: (941) 921-6578 http://faams.net eFAX: (419) 821-5999 =========================================================== |
|
From: Thomas S. <ps...@on...> - 2001-02-16 02:21:19
|
Hal- Thats okay, I like details :) So are you looking to port the Progress 4GL product or enhance an existing product like SQL-Ledger to meet your requirements? 11 taxes! Man, they get you coming, going, and every way in between! I was thinking about the taxes in SQL-Ledger, and to create a better, highly flexible system. I can't figure out a way to take in every tax possibility in a straight foward non-complex fashion. How do you handle it now? -- Thomas Sawyer ps...@on... - email (303) 285-3487 x1594 - voicemail/fax ---- Hal Davison <ha...@fa...> wrote: > On Thu, 15 Feb 2001, you wrote: > > Nice! > > > > That's right, I remember now...Postgresql doesn't have a simple means > > for dropping columns. I think you did the only thing you could do. > This > > transfers your data I take it? Hopefully this will be simplified > in future > > versions of Postgresql. By the way, what are you working on? > > > Well, > > I have a current product done in the Progress 4GL product(NON-SQL) > with the > servers running Caldera 2.3(2.2.14) boxes. Clients connect from Win95/98 > boxes > by TCP/IP and NetTerm over 100BaseT networks. > > The product is designed for petroleum and lubricant distribution jobbers > including a 'BackOffice' package for their C-Stores. > > I has all of the accounting packages including multi-state US payrolls. > > This market is odd in that all unit pricing is done to 5 decimal places. > On any > particular invoice there could be as many as 11 different taxes that > might have > to be computed, added and displayed individually. > > Moving to PostgreSQL so that we can use the various SQL report writers > and the > GUI garbage that the users think they want. > > > Sorry for the long reply..:( > > --Hal. > =========================================================== > Hal Davison Internet Petroleum Gateway > Davison Consulting Caldera 2.2.14 eServer > 6850 Myakka Valley Tr PostgreSQL 7.03 - Sun Forte - JAVA > Sarasota, Florida 34241 Phone: (941) 921-6578 > http://faams.net eFAX: (419) 821-5999 > =========================================================== > > __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com |
|
From: Hal D. <ha...@fa...> - 2001-02-16 06:02:19
|
On Thu, 15 Feb 2001, you wrote: > Hal- > > Thats okay, I like details :) > > So are you looking to port the Progress 4GL product or enhance an existing > product like SQL-Ledger to meet your requirements? > > 11 taxes! Man, they get you coming, going, and every way in between! > I was thinking about the taxes in SQL-Ledger, and to create a better, > highly flexible system. I can't figure out a way to take in every tax > possibility in a straight foward non-complex fashion. How do you handle > it now? Tom, Prolly the best way for you to see how our excise taxes are structured is visit my web thinggy at http://www.faams.net There is an entire section devoted to the EXCISE Tax feature. This is a presentation from a users point of view. If you would like further progromatic detail and concepts, I can do that as well. Should we take this discussion 'Off-List' or keep it here? Don't want to munge the Signal/Noise ratio because I like everyone else am a guest here. --Hal. =========================================================== Hal Davison Internet Petroleum Gateway Davison Consulting Caldera 2.2.14 eServer 6850 Myakka Valley Tr PostgreSQL 7.03 - Sun Forte - JAVA Sarasota, Florida 34241 Phone: (941) 921-6578 http://faams.net eFAX: (419) 821-5999 =========================================================== |
|
From: Pati D. <pa...@se...> - 2001-02-15 22:41:50
|
Well Tom,
Answer ain't there..but..did find:
SELECT (..All columns except the one that you drop...)
INTO TABLE tmp_name
FROM old_table;
DROP TABLE old_table;
ALTER TABLE tmp_table RENAME TO old_table;
This will do the trick..!!
----- Original Message -----
From: Thomas Sawyer <ps...@on...>
To: <sql...@li...>
Sent: Thursday, February 15, 2001 5:19 PM
Subject: Re: [SQL-Ledger-users] Drop Column?
| As the postgres user, run "psql". At the psql prompt type \h to see help.
| type \h {command_name} to get more specific help.
|
| --
| Thomas Sawyer
| ps...@on... - email
| (303) 285-3487 x1594 - voicemail/fax
|
|
|
| ---- Hal Davison <ha...@fa...> wrote:
| >
| > If there is a column that one creates by mistake, what is the PostgeSQL
| > function/command that is used to DROP the COLUNM?
| >
| >
| > --Hal.
| > ===========================================================
| > Hal Davison Internet Petroleum Gateway
| > Davison Consulting Caldera 2.2.14 eServer
| > 6850 Myakka Valley Tr PostgreSQL 7.03 - Sun Forte - JAVA
| > Sarasota, Florida 34241 Phone: (941) 921-6578
| > http://faams.net eFAX: (419) 821-5999
| > ===========================================================
| >
| >
|
| __________________________________________________
| FREE voicemail, email, and fax...all in one place.
| Sign Up Now! http://www.onebox.com
|
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X