Re: COPY to table with array columns (Longish)
От | Phillip Smith |
---|---|
Тема | Re: COPY to table with array columns (Longish) |
Дата | |
Msg-id | 003c01c68f4c$9fd487b0$9b0014ac@ITPhil обсуждение исходный текст |
Ответ на | Re: COPY to table with array columns (Longish) ("Aaron Bono" <postgresql@aranya.com>) |
Список | pgsql-sql |
No, it was me that didn't understand!! But I do now - quite simple really! Cheers, -p -----Original Message----- From: pgsql-sql-owner@postgresql.org [mailto:pgsql-sql-owner@postgresql.org] On Behalf Of Aaron Bono Sent: Wednesday, 14 June 2006 10:41 AM To: phillips@weatherbeeta.com.au Cc: pgsql-sql@postgresql.org Subject: Re: [SQL] COPY to table with array columns (Longish) I guess I still don't understand... If you take the approach operationsengineer1 and I suggested, you should only need 3 or 4 tables regardless of the number of SYS file records. Good luck with your implementation. -Aaron On 6/13/06, Phillip Smith <phillips@weatherbeeta.com.au> wrote: > Thanks Aaron - There are currently 8175 records in my SYS file - I might > need to go with this approach but be selective about which items I export so > I don't end up with 8000 tables related to SYS! There's probably a lot of > **** in there that doesn't actually need to be exported. > > Thanks again, > -p ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.orgso that your message can get through to the mailing list cleanly *******************Confidentiality and Privilege Notice******************* The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments
В списке pgsql-sql по дате отправления: