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



Andreas Säger wrote

Why can't you run SQL update queries? This is trivial to do in SQL. The 
SQL is trivial to execute by macro.
If you desparately want a graphical query designer for 
update/insert/delete queries, then you should write one and store your 
queries somewhere in the .odb container.


Of course I can. If I can find out how to do it. 

But this isn't the point, is it? The real point is that database front-ends
and macro languages are meant to make life easy, not difficult. You seem to
dislike "sugar" - worried about your diameter? The computer was made for
man, not man for the computer. Why not program in assembler - gives you much
more control and isn't really that hard (I speak from years of assembler
experience and with my tongue firmly in my cheek)?

-----
Peter
--
View this message in context: 
http://nabble.documentfoundation.org/Problems-importing-an-OO-database-into-LO-tp3890826p3916735.html
Sent from the Users mailing list archive at Nabble.com.

-- 
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.