[campsite-dev] Database template request - Newscoop Development Discussions on Sourcefabric Forum

import

Please anyone,
I asked several month ago to increase Password field size in database
from 32 to 42, because on MySQL 4.1 the crypt generates longer strings.
I asked about that in 2.2.2
We have 2.3.1 and the size 32 is still there.

Please. is it possible to set 42 as default at least for the newly
created databases? On FreeBSD I can add it to a list of patches I use,
but this is common issue in all OSes so I would prefer to do that in
default campsite CVS and have it corrected in 2.3.2 or any next release.

Ondra

import

I've put it in as a bug for 2.3.2, which we are hoping to release on
Wednesday.

Ondra Koutek wrote:
> Please anyone,
> I asked several month ago to increase Password field size in database
> from 32 to 42, because on MySQL 4.1 the crypt generates longer strings.
> I asked about that in 2.2.2
> We have 2.3.1 and the size 32 is still there.
>
> Please. is it possible to set 42 as default at least for the newly
> created databases? On FreeBSD I can add it to a list of patches I use,
> but this is common issue in all OSes so I would prefer to do that in
> default campsite CVS and have it corrected in 2.3.2 or any next release.
>
> Ondra
>

import

Can't fix it in 2.3.2 because the database changes can happen only in minor
versions, not bugfix versions. I moved it to 2.4.0

Mugur

--- Paul Baranowski wrote:
> I've put it in as a bug for 2.3.2, which we are hoping to release on
> Wednesday.
>
>
> Ondra Koutek wrote:
> > Please anyone,
> > I asked several month ago to increase Password field size in database
> > from 32 to 42, because on MySQL 4.1 the crypt generates longer strings.
> > I asked about that in 2.2.2
> > We have 2.3.1 and the size 32 is still there.
> >
> > Please. is it possible to set 42 as default at least for the newly
> > created databases? On FreeBSD I can add it to a list of patches I use,
> > but this is common issue in all OSes so I would prefer to do that in
> > default campsite CVS and have it corrected in 2.3.2 or any next release.
> >
> > Ondra
> >
>
>

__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs

import

I do not care much about this, until I forget to patch my campsite
installations manually after upgrade, but I consider this step as
mistake.
Most of current OSes use 4.1 as standard and we already know, that 2.3.2
which is not released yet will not work on current systems.

If I were you, I would release 2.3.2 with dirty hack (increasing
password fields only for new instances) which will help new users, old
users can alter their tables manually if they want (and if they use 4.1
they had to do that already anyways), so you loose 30secs of your time
to do this hack, but allow 75% of new users to have no problems with
install.
Than with 2.4.0 I would run "update_instance" with altering all campsite
databases to proper value.

Ondra

On Tue, 2005-10-11 at 05:19 -0700, Mugur Rus wrote:
> Can't fix it in 2.3.2 because the database changes can happen only in minor
> versions, not bugfix versions. I moved it to 2.4.0
>
> Mugur
>
> --- Paul Baranowski wrote:
> > I've put it in as a bug for 2.3.2, which we are hoping to release on
> > Wednesday.
> >
> >
> > Ondra Koutek wrote:
> > > Please anyone,
> > > I asked several month ago to increase Password field size in database
> > > from 32 to 42, because on MySQL 4.1 the crypt generates longer strings.
> > > I asked about that in 2.2.2
> > > We have 2.3.1 and the size 32 is still there.
> > >
> > > Please. is it possible to set 42 as default at least for the newly
> > > created databases? On FreeBSD I can add it to a list of patches I use,
> > > but this is common issue in all OSes so I would prefer to do that in
> > > default campsite CVS and have it corrected in 2.3.2 or any next release.
> > >
> > > Ondra
> > >
> >
> >
>
>
>
>
> __________________________________
> Start your day with Yahoo! - Make it your home page!
> http://www.yahoo.com/r/hs

import

I have MySQL 4.1 installed and didn't have problems with the password due to
field length. Maybe it's because of custom configuration of MySQL server. I
don't have time to write a dirty hack, too much work, could you do it?

Mugur

--- Ondra Koutek wrote:
> I do not care much about this, until I forget to patch my campsite
> installations manually after upgrade, but I consider this step as
> mistake.
> Most of current OSes use 4.1 as standard and we already know, that 2.3.2
> which is not released yet will not work on current systems.
>
> If I were you, I would release 2.3.2 with dirty hack (increasing
> password fields only for new instances) which will help new users, old
> users can alter their tables manually if they want (and if they use 4.1
> they had to do that already anyways), so you loose 30secs of your time
> to do this hack, but allow 75% of new users to have no problems with
> install.
> Than with 2.4.0 I would run "update_instance" with altering all campsite
> databases to proper value.
>
> Ondra
>
> On Tue, 2005-10-11 at 05:19 -0700, Mugur Rus wrote:
> > Can't fix it in 2.3.2 because the database changes can happen only in minor
> > versions, not bugfix versions. I moved it to 2.4.0
> >
> > Mugur
> >
> > --- Paul Baranowski wrote:
> > > I've put it in as a bug for 2.3.2, which we are hoping to release on
> > > Wednesday.
> > >
> > >
> > > Ondra Koutek wrote:
> > > > Please anyone,
> > > > I asked several month ago to increase Password field size in database
> > > > from 32 to 42, because on MySQL 4.1 the crypt generates longer strings.
> > > > I asked about that in 2.2.2
> > > > We have 2.3.1 and the size 32 is still there.
> > > >
> > > > Please. is it possible to set 42 as default at least for the newly
> > > > created databases? On FreeBSD I can add it to a list of patches I use,
> > > > but this is common issue in all OSes so I would prefer to do that in
> > > > default campsite CVS and have it corrected in 2.3.2 or any next
> release.
> > > >
> > > > Ondra
> > > >
> > >
> > >
> >
> >
> >
> >
> > __________________________________
> > Start your day with Yahoo! - Make it your home page!
> > http://www.yahoo.com/r/hs
>
>

__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com

import

file: implementation/database/campsite-db.sql
line: 798:
change: `Password` varchar(32) NOT NULL default '',
to:`Password` varchar(42) NOT NULL default '',

That will fix new instances. (may be it is only FreeBSD and Fedora4
issue, I did not tested other distros)
For upgrading old instances, you need to add one sql command to
upgrade_instance altering the old structure:
alter table Users modify Password varchar(42) NOT NULL default '';
for each upgraded instance. It will not affect anything badly if you do
that each install, and you can do it in smarter way when you have time.

Ondra

On Thu, 2005-10-13 at 09:00 -0700, Mugur Rus wrote:
> I have MySQL 4.1 installed and didn't have problems with the password due to
> field length. Maybe it's because of custom configuration of MySQL server. I
> don't have time to write a dirty hack, too much work, could you do it?
>
> Mugur
>
> --- Ondra Koutek wrote:
> > I do not care much about this, until I forget to patch my campsite
> > installations manually after upgrade, but I consider this step as
> > mistake.
> > Most of current OSes use 4.1 as standard and we already know, that 2.3.2
> > which is not released yet will not work on current systems.
> >
> > If I were you, I would release 2.3.2 with dirty hack (increasing
> > password fields only for new instances) which will help new users, old
> > users can alter their tables manually if they want (and if they use 4.1
> > they had to do that already anyways), so you loose 30secs of your time
> > to do this hack, but allow 75% of new users to have no problems with
> > install.
> > Than with 2.4.0 I would run "update_instance" with altering all campsite
> > databases to proper value.
> >
> > Ondra
> >
> > On Tue, 2005-10-11 at 05:19 -0700, Mugur Rus wrote:
> > > Can't fix it in 2.3.2 because the database changes can happen only in minor
> > > versions, not bugfix versions. I moved it to 2.4.0
> > >
> > > Mugur
> > >
> > > --- Paul Baranowski wrote:
> > > > I've put it in as a bug for 2.3.2, which we are hoping to release on
> > > > Wednesday.
> > > >
> > > >
> > > > Ondra Koutek wrote:
> > > > > Please anyone,
> > > > > I asked several month ago to increase Password field size in database
> > > > > from 32 to 42, because on MySQL 4.1 the crypt generates longer strings.
> > > > > I asked about that in 2.2.2
> > > > > We have 2.3.1 and the size 32 is still there.
> > > > >
> > > > > Please. is it possible to set 42 as default at least for the newly
> > > > > created databases? On FreeBSD I can add it to a list of patches I use,
> > > > > but this is common issue in all OSes so I would prefer to do that in
> > > > > default campsite CVS and have it corrected in 2.3.2 or any next
> > release.
> > > > >
> > > > > Ondra
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Start your day with Yahoo! - Make it your home page!
> > > http://www.yahoo.com/r/hs
> >
> >
>
>
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com

import

Ondra, the upgrade thing is not that simple: I would have to customise it to
perform a certain operation specificaly for 2.3.2, which would make it more
complicated and would break the script workflow. And I don't want that because
it will make my life miserable later.

Mugur

--- Ondra Koutek wrote:
> file: implementation/database/campsite-db.sql
> line: 798:
> change: `Password` varchar(32) NOT NULL default '',
> to:`Password` varchar(42) NOT NULL default '',
>
> That will fix new instances. (may be it is only FreeBSD and Fedora4
> issue, I did not tested other distros)
> For upgrading old instances, you need to add one sql command to
> upgrade_instance altering the old structure:
> alter table Users modify Password varchar(42) NOT NULL default '';
> for each upgraded instance. It will not affect anything badly if you do
> that each install, and you can do it in smarter way when you have time.
>
> Ondra
>
>
> On Thu, 2005-10-13 at 09:00 -0700, Mugur Rus wrote:
> > I have MySQL 4.1 installed and didn't have problems with the password due
> to
> > field length. Maybe it's because of custom configuration of MySQL server. I
> > don't have time to write a dirty hack, too much work, could you do it?
> >
> > Mugur
> >
> > --- Ondra Koutek wrote:
> > > I do not care much about this, until I forget to patch my campsite
> > > installations manually after upgrade, but I consider this step as
> > > mistake.
> > > Most of current OSes use 4.1 as standard and we already know, that 2.3.2
> > > which is not released yet will not work on current systems.
> > >
> > > If I were you, I would release 2.3.2 with dirty hack (increasing
> > > password fields only for new instances) which will help new users, old
> > > users can alter their tables manually if they want (and if they use 4.1
> > > they had to do that already anyways), so you loose 30secs of your time
> > > to do this hack, but allow 75% of new users to have no problems with
> > > install.
> > > Than with 2.4.0 I would run "update_instance" with altering all campsite
> > > databases to proper value.
> > >
> > > Ondra
> > >
> > > On Tue, 2005-10-11 at 05:19 -0700, Mugur Rus wrote:
> > > > Can't fix it in 2.3.2 because the database changes can happen only in
> minor
> > > > versions, not bugfix versions. I moved it to 2.4.0
> > > >
> > > > Mugur
> > > >
> > > > --- Paul Baranowski wrote:
> > > > > I've put it in as a bug for 2.3.2, which we are hoping to release on
> > > > > Wednesday.
> > > > >
> > > > >
> > > > > Ondra Koutek wrote:
> > > > > > Please anyone,
> > > > > > I asked several month ago to increase Password field size in
> database
> > > > > > from 32 to 42, because on MySQL 4.1 the crypt generates longer
> strings.
> > > > > > I asked about that in 2.2.2
> > > > > > We have 2.3.1 and the size 32 is still there.
> > > > > >
> > > > > > Please. is it possible to set 42 as default at least for the newly
> > > > > > created databases? On FreeBSD I can add it to a list of patches I
> use,
> > > > > > but this is common issue in all OSes so I would prefer to do that
> in
> > > > > > default campsite CVS and have it corrected in 2.3.2 or any next
> > > release.
> > > > > >
> > > > > > Ondra
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Start your day with Yahoo! - Make it your home page!
> > > > http://www.yahoo.com/r/hs
> > >
> > >
> >
> >
> >
> >
> >
> > __________________________________
> > Yahoo! Mail - PC Magazine Editors' Choice 2005
> > http://mail.yahoo.com
>
>

__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs

import

OK, than on my server and on SNOW we had to do this to be able to
login.
I did not realise any problems, but I am sure you know what are you
talking about.
So postpone that to 2.4.

Ondra

On Fri, 2005-10-14 at 01:24 -0700, Mugur Rus wrote:
> Ondra, the upgrade thing is not that simple: I would have to customise it to
> perform a certain operation specificaly for 2.3.2, which would make it more
> complicated and would break the script workflow. And I don't want that because
> it will make my life miserable later.
>
> Mugur
>
> --- Ondra Koutek wrote:
> > file: implementation/database/campsite-db.sql
> > line: 798:
> > change: `Password` varchar(32) NOT NULL default '',
> > to:`Password` varchar(42) NOT NULL default '',
> >
> > That will fix new instances. (may be it is only FreeBSD and Fedora4
> > issue, I did not tested other distros)
> > For upgrading old instances, you need to add one sql command to
> > upgrade_instance altering the old structure:
> > alter table Users modify Password varchar(42) NOT NULL default '';
> > for each upgraded instance. It will not affect anything badly if you do
> > that each install, and you can do it in smarter way when you have time.
> >
> > Ondra
> >
> >
> > On Thu, 2005-10-13 at 09:00 -0700, Mugur Rus wrote:
> > > I have MySQL 4.1 installed and didn't have problems with the password due
> > to
> > > field length. Maybe it's because of custom configuration of MySQL server. I
> > > don't have time to write a dirty hack, too much work, could you do it?
> > >
> > > Mugur
> > >
> > > --- Ondra Koutek wrote:
> > > > I do not care much about this, until I forget to patch my campsite
> > > > installations manually after upgrade, but I consider this step as
> > > > mistake.
> > > > Most of current OSes use 4.1 as standard and we already know, that 2.3.2
> > > > which is not released yet will not work on current systems.
> > > >
> > > > If I were you, I would release 2.3.2 with dirty hack (increasing
> > > > password fields only for new instances) which will help new users, old
> > > > users can alter their tables manually if they want (and if they use 4.1
> > > > they had to do that already anyways), so you loose 30secs of your time
> > > > to do this hack, but allow 75% of new users to have no problems with
> > > > install.
> > > > Than with 2.4.0 I would run "update_instance" with altering all campsite
> > > > databases to proper value.
> > > >
> > > > Ondra
> > > >
> > > > On Tue, 2005-10-11 at 05:19 -0700, Mugur Rus wrote:
> > > > > Can't fix it in 2.3.2 because the database changes can happen only in
> > minor
> > > > > versions, not bugfix versions. I moved it to 2.4.0
> > > > >
> > > > > Mugur
> > > > >
> > > > > --- Paul Baranowski wrote:
> > > > > > I've put it in as a bug for 2.3.2, which we are hoping to release on
> > > > > > Wednesday.
> > > > > >
> > > > > >
> > > > > > Ondra Koutek wrote:
> > > > > > > Please anyone,
> > > > > > > I asked several month ago to increase Password field size in
> > database
> > > > > > > from 32 to 42, because on MySQL 4.1 the crypt generates longer
> > strings.
> > > > > > > I asked about that in 2.2.2
> > > > > > > We have 2.3.1 and the size 32 is still there.
> > > > > > >
> > > > > > > Please. is it possible to set 42 as default at least for the newly
> > > > > > > created databases? On FreeBSD I can add it to a list of patches I
> > use,
> > > > > > > but this is common issue in all OSes so I would prefer to do that
> > in
> > > > > > > default campsite CVS and have it corrected in 2.3.2 or any next
> > > > release.
> > > > > > >
> > > > > > > Ondra
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > __________________________________
> > > > > Start your day with Yahoo! - Make it your home page!
> > > > > http://www.yahoo.com/r/hs
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Yahoo! Mail - PC Magazine Editors' Choice 2005
> > > http://mail.yahoo.com
> >
> >
>
>
>
>
> __________________________________
> Start your day with Yahoo! - Make it your home page!
> http://www.yahoo.com/r/hs

Howdy, Stranger!

Categories

Poll

Top Posters