Hi Mike
Thanks very much. It’s a shame they broke it so badly! I’ll change to your
recommendation immediately.
Cheers
Warwick
Warwick A. Prince
Mushroom Systems International Pty. Ltd.
> On 5 Mar 2019, at 3:07 am, Mike Bayer wrote:
>
>> On Sun, Mar 3, 2019 at 8:40 PM Warwick Prince
>>
On Tue, 5 Mar 2019, Mike Bayer wrote:
sure, if your PG database allows you to connect using "trust" or other
localhost-style connection you can omit everything from the URL
Thanks, Mike.
Yes, I have all hosts on the LAN set to trust as nothing is exposed to the
world.
Best regards,
Rich
sure, if your PG database allows you to connect using "trust" or other
localhost-style connection you can omit everything from the URL
create_engine("postgresql://localhost/dbname")
or
create_engine("postgresql://user@localhost/dbname")
create_engine("postgresql:///dbname")
etc
On Tue, Mar
I'm writing an application for my business use; I'll be the only user and
postgres is on the same server/workstation host. When I specify the engine
using create_engine() can I leave off at least my password if not both it
and my username? The database to which SA is connecting is owned by me.
Also there's a long term plan to remove classical mappings as a first
class feature, replacing it with an equivalent function that applies
declarative mapping to a class.There isn't a plan to have a
"clear_mappers()" in this case, the way you clear a mapping for a
class is that you stop using
The individual mapper clear process is via the mapper.dispose()
method. The individual class that was mapped will be de-instrumented
and act like a regular Python class.
The next steps to take depend very highly on what kind of mappings you
are using and what you are trying to do.
On Tue, Mar
