Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On Fri, 21 Dec 2012, Rich Shepard wrote:

 I've been going around in circles on this issue for most of today without
finding the solution. The context:

  The reason for the problem, and its solution, finally penetrated my
consciousness so I resolved the issue.

  Usually, the data I get in spreadsheet format has a value in each cell so
I can write the SQL INSERT INTO statement without specifying column names for
each value; each row is complete. With these data, however, there are
missing values which are different in each row. Therefore, I need to either
specify the attributes with values for each row in the INSERT INTO statement
or indicate blanks with NULLs.

  Because each spreadsheet can have 19-100 columns and up to 105,000 rows,
hand-crafting an INSERT INTO statement for each file would require a huge
amount of time. Ergo, I'm filling in blank cells with NA which is easily
converted to NULL once the table exists in postgres.

  Thanks for all the suggestions, and the best of the holiday season to
everyone.

Rich


--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.