--- Received from FPU.WHITES1 799 3703                       30-10-01 10:31

  -> [EMAIL PROTECTED]

Agreed.  In my experience ODBC can rarely handle 'production' load, though
fine for simple personal apps.  Other problem relating to ODBC is that to be
truly backend independent you have to really use the api.  No good just
building some recordsets in MSVC++ and expecting them to work with different
backend systems.  There are just too many differences between them to have a
static mechanism handle them - the type mapping alone blows this out of the
water (except for pretty trivial schemas).

For a truly backend independent ODBC app you need to have active code
talking to the (pretty enormous) ODBC API to work out exactly how it should
be talking to the database, and that's so much grief you might as well just
plump for a backend of choice with a decent direct api, abstract it in your
own code, get better performance and save a lot of time and effort!  I've
learnt this lesson the hard way 8-(

-Steve

----------------------------------------------------------------------------

From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: Tue, 30 Oct 2001 02:53:52 +0100
Subject: RE: [PHP-WIN] Help, connection object in php

Sort of. The main purpose with ODBC is though to scale away the lower layers
of setting up a connection - making it target independent, but also get rid
about having to think about which kind of network protocol to use, etc, etc.


Once encapsulating all boring stuff of ODBC in C++ objects it gets in fact
quite nice to work with, but according to my experience larger bulk inserts
starts to behave strange with ODBC (I am talking about doing several hundred
of thousand or millions of inserts in one single run.)

A common mistake when one migrate a database and hence have to change the
ODBC connection is to forget to create the user account on the target RDBMS
- of course causing connection problem - this might, by the way, be the
problem Aaron experience right now - but for now I lack enough information
to be able to judge on that one. To be continued. :)

So I wouldn't say it hazzle free, but still easier - but only once
everything is set up properly. ;)

-----Original Message-----
From: Ross Fleming
To: aaron; [EMAIL PROTECTED]
Sent: 2001-10-30 02:32
Subject: RE: [PHP-WIN] Help, connection object in php

Forgive my ignorance but doesn't ODBC do this for you, pretty much
hassle free?  I've only briefly looked into this once though.

Ross

PS I've REALLY only dabbled in this when tossing an idea over in my
head, I
should really have a disclaimer:
The above statements could well be a load of ^%%&!!  Feel free to
ridicule
them.  :)

-----Original Message-----
From: aaron [mailto:[EMAIL PROTECTED]]
Sent: 29 October 2001 18:17
To: [EMAIL PROTECTED]
Subject: [PHP-WIN] Help, connection object in php


Is is possible to set the connection object to point to a database on
another server?  I'm using SQLserver and IIS and would like to point the
connection object to the SQL server.  SQL server is on one computer and
IIS
is on another.

Thanks,
Aaron





--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

This e-mail may contain confidential information and/or copyright
material. This e-mail is intended for the use of the addressee
only. Any unauthorised use may be unlawful.

If you receive this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software.

Friends Provident Marketing Group consists of the following
companies:

Friends Provident Life and Pensions Limited.
Registered number 4096141.
Friends' Provident Unit Trust Managers Limited.
Registered number 970641
FP Life Assurance Limited.
Registered number 782698
Friends Provident Pensions Limited.
Registered number 475201
Friends Ivory & Sime Managed Pensions Funds Limited.
Registered number 1020044
Registered and Head Office of each of the above companies is at Pixham End,
Dorking, Surrey RH4 1QA.
Registered in England. Incorporated companies limited by shares.
Ivory & Sime Trustlink Limited. Registered number 151198
Registered and Head Office: One Charlotte Square, Edinburgh EH2
4DZ.  Registered in Scotland. Incorporated company limited by
shares.

Companies within this Group transact life assurance, pension,
permanent health, unit trust and investment trust business

All are regulated by the Personal Investment Authority.
Friends' Provident Unit Trust Managers Limited is also regulated
by IMRO.

--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to