[MonetDB-users] COPY...INTO from remote
I noticed that COPY...INTO from a file, when executed from a remote MonetDB mclient instance tries to load the file from the system that the database is actually running on rather than the system running the remote client. Is this the expected behavior? Has anyone dealt with this or found another way to batch-load from a remote client? 73, Matthew W. Jones (KI4ZIB) http://matburt.net
I noticed that COPY...INTO from a file, when executed from a remote MonetDB mclient instance tries to load the file from the system that the database is actually running on rather than the system running the remote client. Ofcourse. You sent a statement to a SQL server, it is interpreted in that context.
Is this the expected behavior? Has anyone dealt with this or found another way to batch-load from a remote client? you might use COPY FROM stdin in combination with
Hi Matthew
Matthew Jones wrote:
the mclient directive \ 73,
Matthew W. Jones (KI4ZIB)
http://matburt.net ------------------------------------------------------------------------ ------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july ------------------------------------------------------------------------ _______________________________________________
MonetDB-users mailing list
MonetDB-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/monetdb-users
Thanks Martin, this certainly sounds like it will work fine. This is an
extension of trying to do this from the Python API (same behavior as
executing it from mclient) so it means spawning a new process and executing
a shell command instead of going through the API.
The new Python API implementation is great, keep up the good work.
73,
Matthew W. Jones (KI4ZIB)
http://matburt.net
On Thu, Aug 6, 2009 at 2:42 PM, Martin Kersten
Hi Matthew
I noticed that COPY...INTO from a file, when executed from a remote MonetDB mclient instance tries to load the file from the system that the database is actually running on rather than the system running the remote client. Ofcourse. You sent a statement to a SQL server, it is interpreted in that context.
Is this the expected behavior? Has anyone dealt with this or found another way to batch-load from a remote client? you might use COPY FROM stdin in combination with
Matthew Jones wrote: the mclient directive \
73, Matthew W. Jones (KI4ZIB) http://matburt.net
------------------------------------------------------------------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------
_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On 06-08-2009 14:49:47 -0400, Matthew Jones wrote:
Thanks Martin, this certainly sounds like it will work fine. This is an extension of trying to do this from the Python API (same behavior as executing it from mclient) so it means spawning a new process and executing a shell command instead of going through the API. The new Python API implementation is great, keep up the good work.
Given how it works, it should be easy to do this from Python without a fork, but Gijs should be able to fill you in on the details.
participants (3)
-
Fabian Groffen -
Martin Kersten -
Matthew Jones