Midcom 2.6 schema and sql files

[Tarjei Huse-8]

Hi, with MidCOM 2.6 comming along nicely, I'm starting to wonder how
poeple are planning to get the midgard tables updated for the extra
MidCOM schemas.

As I see it there are a few options:
1. Release MidCOM with 1.8 only.
-> Risky as we do not know when 1.8 will be out.

2. Release Midcom for 1.7 with a simple update script as a stopgap measure.

Item (2) raises tow new questions:
a) Should this release be done with pear?
b) If if should be done with pear, how should we package and run the
tableupdates?

I'm wondering as I'm trying to get the pear installations running on the
testbox and I see this and the issues on static dirs as the main
problems at the moment.
Regards,
Tarjei

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

[Piotras]

tarjei <tarjei@...> wrote:

> 2. Release Midcom for 1.7 with a simple update script as a stopgap measure.
>
> Item (2) raises tow new questions:
> a) Should this release be done with pear?

Absolutely not.

> b) If if should be done with pear, how should we package and run the
> tableupdates?

The same way as dg handles it now. But pearized MidCOM is not going to be
included in some 1.7 release.
If we need this , we need to move dg from HEAD to 1-7 branch.
 
> I'm wondering as I'm trying to get the pear installations running on the
> testbox and I see this and the issues on static dirs as the main
> problems at the moment.

1. Tables create and update.

a) Use midgard-schema
b) DG automagically handles sql files placed in sql/update subdirectory.

2. I have no idea about static dirs and pear.

3. DG in HEAD supports pear and pearized midcom. This is initial as I still
do not know what packages should be installed.

Piotras

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

[Tarjei Huse-8]

Piotras wrote:

> tarjei <tarjei@...> wrote:
>
>> 2. Release Midcom for 1.7 with a simple update script as a stopgap measure.
>>
>> Item (2) raises tow new questions:
>> a) Should this release be done with pear?
>
> Absolutely not.
>
>> b) If if should be done with pear, how should we package and run the
>> tableupdates?
>
> The same way as dg handles it now. But pearized MidCOM is not going to be
> included in some 1.7 release.
> If we need this , we need to move dg from HEAD to 1-7 branch.

>> I'm wondering as I'm trying to get the pear installations running on the
>> testbox and I see this and the issues on static dirs as the main
>> problems at the moment.
>
> 1. Tables create and update.
>
> a) Use midgard-schema
> b) DG automagically handles sql files placed in sql/update subdirectory.
Bergie, could we have a midgard_sql directory configuration item?


> 2. I have no idea about static dirs and pear.
>
> 3. DG in HEAD supports pear and pearized midcom. This is initial as I still
> do not know what packages should be installed.
Take a look on the testhost. The pearsetup there is fairly complete. I
think you'll probably see you're missing some pear commands.

Tarjei
>
> Piotras
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@...
> For additional commands, e-mail: user-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

[Henri Bergius]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 24, 2006, at 12:02, Tarjei Huse wrote:
>> 1. Tables create and update.
>> a) Use midgard-schema
>> b) DG automagically handles sql files placed in sql/update  
>> subdirectory.
> Bergie, could we have a midgard_sql directory configuration item?

We could create another custom role for this, yes. Even after midgard-
schema table creation this could be useful for adding indexes, etc.

Any preferences on the location? Maybe config/database.sql ?

> Tarjei

/Bergie

Henri Bergius
Consultant Partner, Nemein
henri.bergius@...

Midgard CMS
www.midgard-project.org



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFD/toyNkT8k497k9IRAnMeAJ9Es1a1ViSViMDNKoxMvNZlSpaLxACfVwh5
NIfw9UGDPI1UUE00W2uINcg=
=6YC3
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...