Development

#1258 (Use propel.ini connection settings for propel-load-data task instead of databases.yml)

You must first sign up to be able to contribute.

Ticket #1258 (new enhancement)

Opened 2 years ago

Last modified 4 months ago

Use propel.ini connection settings for propel-load-data task instead of databases.yml

Reported by: francois Assigned to: fabien
Priority: minor Milestone: 1.2.0
Component: tasks Version: 1.1.0 DEV
Keywords: Cc:
Qualification: Design decision

Description

The propel-load-data task currently requires an application name to run , so that it finds connection settings in a databases.yml. But all the other Propel related tasks use the propel.ini configuration for figuring out connection settings. For uniformity, propel-load-data shoud do the same.

It means that the propel-load-data and propel-build-all-load should not require an application name anymore.

This should also solve #1244.

Change History

01/05/07 17:58:11 changed by fabien

  • milestone set to post-1.0.

02/26/08 05:17:49 changed by Carl.Vondrick

  • owner set to fabien.
  • component set to tasks.
  • qualification set to Unreviewed.

05/10/08 22:43:20 changed by fabien

  • milestone deleted.

06/23/08 07:06:25 changed by dwhittle

  • version set to 1.1.0 DEV.
  • qualification changed from Unreviewed to Design decision.
  • milestone set to 1.2.0.