Menu
▾
▴
slashcode-development — This list is for development of slashcode, no install questions please.
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(29) |
Dec
(101) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(90) |
Feb
(101) |
Mar
(173) |
Apr
(141) |
May
(38) |
Jun
(28) |
Jul
(14) |
Aug
(7) |
Sep
(3) |
Oct
(7) |
Nov
(15) |
Dec
(9) |
| 2002 |
Jan
(2) |
Feb
(5) |
Mar
(11) |
Apr
|
May
(4) |
Jun
(6) |
Jul
(7) |
Aug
(12) |
Sep
(8) |
Oct
(1) |
Nov
(4) |
Dec
(7) |
| 2003 |
Jan
(7) |
Feb
(1) |
Mar
(9) |
Apr
(2) |
May
(3) |
Jun
(4) |
Jul
(19) |
Aug
(4) |
Sep
(8) |
Oct
(30) |
Nov
(25) |
Dec
(22) |
| 2004 |
Jan
(6) |
Feb
(12) |
Mar
|
Apr
(2) |
May
|
Jun
(10) |
Jul
(18) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2005 |
Jan
(8) |
Feb
(4) |
Mar
(6) |
Apr
(5) |
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(3) |
Dec
|
| 2006 |
Jan
(9) |
Feb
(6) |
Mar
(11) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Eric D. <eri...@ja...> - 2001-04-25 05:36:56
|
hmm.....ok. I just downloaded the tarball of the latest release, and then installed it. Same problem. Chris Nandor wrote: > At 22:17 -0700 2001.04.24, Eric Dannewitz wrote: > >I just CVSuped to the latest Bender release, and I'm getting the > >following error > > There is no bender release anymore. There is only MAIN (no tag) and fry. > If you have checked out with the tag "bender", that could be the cause of > your problems. > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development -- What we have to learn to do, we learn by doing. - Aristotle Eric Dannewitz - Adventurer, saxophonist, good-timer (crook? quite possibly), clarinetist, manic self-publicist, part-time flautist(flutist?), macintosher, and often thought to be completely out to lunch. http://www.jazz-sax.com |
|
From: Chris N. <pu...@po...> - 2001-04-25 05:24:54
|
At 22:17 -0700 2001.04.24, Eric Dannewitz wrote: >I just CVSuped to the latest Bender release, and I'm getting the >following error There is no bender release anymore. There is only MAIN (no tag) and fry. If you have checked out with the tag "bender", that could be the cause of your problems. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Eric D. <eri...@ja...> - 2001-04-25 05:17:01
|
I just CVSuped to the latest Bender release, and I'm getting the
following error
Can't locate object method "sqlTransactionStart" via package
"DBIx::Password"
at
/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Slash/DB/Static/MySQL.pm
line 81.
why am I here? at /usr/local/slash/sbin/slashd line 36
main::END() called at /usr/local/slash/sbin/slashd line 0
eval {...} called at /usr/local/slash/sbin/slashd line 0
Any ideas?
|
|
From: Brian A. <br...@ta...> - 2001-04-24 16:42:04
|
Alessio Bragadini wrote: > > Chris Nandor wrote: > > > OK, thanks to Stephen Clouse, we now have basic Oracle support in Slash 2.0 > > (in CVS). I've tagged it orapatch in MAIN. If it doesn't work, we can > > back out. > > I stopped in fixing the PostgreSQL patch for 1. lack of time > (surprise...) but mostly 2. I was waiting for the fixes to date_format > and similar I submitted some time ago. I will look closely at Oracle > patch anyway. I am sorry tht they have not been made yet. I have been swamped working on other pieces and today was my first day to go through the patches on SF and pick and choose. With luck the couple you did should be in by this evening. -Brian |
|
From: Alessio B. <al...@al...> - 2001-04-24 16:37:05
|
Stephen Clouse wrote: > 1. LOCK TABLES. This is called in a number of places, but I don't understand > why. Because MySQL lacks row-level locking? Yes. It's quite a strange "feature" that's not needed by either Oracle or PostgreSQL. I submitted to patch to transform it into a doLock call that can be overriden by other drivers but it hasn't been accepted or rejected. -- Alessio F. Bragadini al...@al... APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "It is more complicated than you think" -- The Eighth Networking Truth from RFC 1925 |
|
From: Alessio B. <al...@al...> - 2001-04-24 16:32:22
|
Chris Nandor wrote: > OK, thanks to Stephen Clouse, we now have basic Oracle support in Slash 2.0 > (in CVS). I've tagged it orapatch in MAIN. If it doesn't work, we can > back out. I stopped in fixing the PostgreSQL patch for 1. lack of time (surprise...) but mostly 2. I was waiting for the fixes to date_format and similar I submitted some time ago. I will look closely at Oracle patch anyway. -- Alessio F. Bragadini al...@al... APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "It is more complicated than you think" -- The Eighth Networking Truth from RFC 1925 |
|
From: Stephen C. <the...@wa...> - 2001-04-24 16:19:56
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Apr 23, 2001 at 12:34:23PM -0700, Brian Aker wrote: > > 1. LOCK TABLES. This is called in a number of places, but I don't understand > > why. Because MySQL lacks row-level locking? To ensure a consistent > > read/write due to the lack of transactions? Some explanation is necessary > Poor man's transactions. For instance, in user creation it keeps > two users from creating an account with the same name at the same > time. Right. I'll take a harder look at those locks tonight and determine the best thing for Oracle to do (which might be nothing, actually). I'm betting most if not all of these spots would be better suited by a SELECT FOR UPDATE to obtain a row level lock. > > 2. 1=1. This pops up in several where clauses. It looks like a noop to me, > > but something mentioned it was some sort of optimization. MySQL specific, > > perhaps? Oracle just ignores it, from what SQL traces have told me. > Yep, that is what it is. It also tells MySQL to not reset sequences > on tables where "DELETE FROM table_name" happens. Right. I tried searching on mysql.com but their search preferred to ignore the = sign instead (even in a quoted string). > > The other thing I'm wondering is, where is Slash's "main" loop? AutoCommit is a > > pretty major loss on Oracle, so it would be desirable to turn it off and perform > Ask yourself this, is it? Why don't you want the commit to just happen? > To be honest on most pages all there is, is one INSERT that happens > to access_log. Hmmmm...good point. I'm used to my own (day job) apps, which can do 1,000+ inserts in one sitting (complex data warehousing programs, mainly). If it ain't broke, then.... > I have some patches that will change the sqlDO("LOCK") stuff > over to methods. You could override those with commit/rollback > calls. I was actually considering doing that myself, since I have to turn AutoCommit off temporarily to do any type of lock or similar voodoo; Oracle locks get released on commit, so AutoCommit doesn't work very well with them :) I'll see what comes to me in tonight's session. - -- Stephen Clouse <the...@wa...> warpcore.org Founder, Chief Megalomaniac, and Evil Overlord -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQA/AwUBOuWnqd1EXk7JbKbMEQJtpQCg9aLSxZZmvBsWT2Wd71Ro+v5tnXwAoPO3 iCVikJcKdjUjdonpjTRHiH9K =MUuR -----END PGP SIGNATURE----- |
|
From: Brian A. <br...@ta...> - 2001-04-24 06:35:51
|
Stephen Clouse wrote:
> 1. LOCK TABLES. This is called in a number of places, but I don't understand
> why. Because MySQL lacks row-level locking? To ensure a consistent
> read/write due to the lack of transactions? Some explanation is necessary
Poor man's transactions. For instance, in user creation it keeps
two users from creating an account with the same name at the same
time.
> 2. 1=1. This pops up in several where clauses. It looks like a noop to me,
> but something mentioned it was some sort of optimization. MySQL specific,
> perhaps? Oracle just ignores it, from what SQL traces have told me.
Yep, that is what it is. It also tells MySQL to not reset sequences
on tables where "DELETE FROM table_name" happens.
> The other thing I'm wondering is, where is Slash's "main" loop? AutoCommit is a
> pretty major loss on Oracle, so it would be desirable to turn it off and perform
Ask yourself this, is it? Why don't you want the commit to just happen?
To be honest on most pages all there is, is one INSERT that happens
to access_log.
> a single commit after each client request, both for performance and to avoid
> partial writes. I'm looking into doing this but can't determine where it should
> be done at.
Many pages provide feedback on if everything went ok with
INSERTS/UPDATES. So
just doing something like tacking on a commit() would keep the user
from knowing if what they tried to do actually worked.
Keep in mind, outside of a couple of places where we have LOCK calls,
there are no transactions, no need to worry about commit/rollback.
The few locks that exist are where transactions need to occur (and the
MySQL code
within the year will probably go through the came changes). The two
that come to mind are user creation and the call to get maxcomment.
I have some patches that will change the sqlDO("LOCK") stuff
over to methods. You could override those with commit/rollback
calls.
-Brian
--
_______________________________________________________
Brian Aker, br...@ta...
Slashdot Senior Developer
Seattle, Washington
http://tangent.org/~brian/
http://slashdot.org/
_______________________________________________________
You can't grep a dead tree.
|
|
From: Eric D. <eri...@ja...> - 2001-04-24 06:04:00
|
Well, you might want to check http://www.mysql.com/doc/L/O/LOCK_TABLES.html for lock tables Stephen Clouse wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > While doing the Oracle conversion I noticed a few rather quirky things in the > MySQL code that didn't make much sense to me. I just wanted to run these by > someone more knowledgable, to see if I was correct in porting/emulating/removing > them. > > 1. LOCK TABLES. This is called in a number of places, but I don't understand > why. Because MySQL lacks row-level locking? To ensure a consistent > read/write due to the lack of transactions? Some explanation is necessary > so I can determine what's best for Oracle to do in those spots. For the > time being I substituted LOCK TABLE IN EXCLUSIVE MODE, but this is not the > most (read: least) efficient thing to do in Oracle. > > 2. 1=1. This pops up in several where clauses. It looks like a noop to me, > but something mentioned it was some sort of optimization. MySQL specific, > perhaps? Oracle just ignores it, from what SQL traces have told me. > > The other thing I'm wondering is, where is Slash's "main" loop? AutoCommit is a > pretty major loss on Oracle, so it would be desirable to turn it off and perform > a single commit after each client request, both for performance and to avoid > partial writes. I'm looking into doing this but can't determine where it should > be done at. > > If anyone knows the answers, please clue me in. > > - -- > Stephen Clouse <the...@wa...> > warpcore.org Founder, Chief Megalomaniac, and Evil Overlord > > -----BEGIN PGP SIGNATURE----- > Version: PGP 6.5.8 > > iQA/AwUBOuT9Td1EXk7JbKbMEQLPWgCcDkMVtkzMnGh5SU6T/tPtpeCT72AAnRcf > EdvSiBS8aUJmAIDXLbxuqxn5 > =Uubj > -----END PGP SIGNATURE----- > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development -- Back up my hard disk? I can't find the reverse switch! Eric Dannewitz - Adventurer, saxophonist, good-timer (crook? quite possibly), clarinetist, manic self-publicist, part-time flautist(flutist?), macintosher, and often thought to be completely out to lunch. http://www.jazz-sax.com |
|
From: Stephen C. <the...@wa...> - 2001-04-24 04:13:05
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
While doing the Oracle conversion I noticed a few rather quirky things in the
MySQL code that didn't make much sense to me. I just wanted to run these by
someone more knowledgable, to see if I was correct in porting/emulating/removing
them.
1. LOCK TABLES. This is called in a number of places, but I don't understand
why. Because MySQL lacks row-level locking? To ensure a consistent
read/write due to the lack of transactions? Some explanation is necessary
so I can determine what's best for Oracle to do in those spots. For the
time being I substituted LOCK TABLE IN EXCLUSIVE MODE, but this is not the
most (read: least) efficient thing to do in Oracle.
2. 1=1. This pops up in several where clauses. It looks like a noop to me,
but something mentioned it was some sort of optimization. MySQL specific,
perhaps? Oracle just ignores it, from what SQL traces have told me.
The other thing I'm wondering is, where is Slash's "main" loop? AutoCommit is a
pretty major loss on Oracle, so it would be desirable to turn it off and perform
a single commit after each client request, both for performance and to avoid
partial writes. I'm looking into doing this but can't determine where it should
be done at.
If anyone knows the answers, please clue me in.
- --
Stephen Clouse <the...@wa...>
warpcore.org Founder, Chief Megalomaniac, and Evil Overlord
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBOuT9Td1EXk7JbKbMEQLPWgCcDkMVtkzMnGh5SU6T/tPtpeCT72AAnRcf
EdvSiBS8aUJmAIDXLbxuqxn5
=Uubj
-----END PGP SIGNATURE-----
|
|
From: Chris N. <pu...@po...> - 2001-04-23 21:04:27
|
OK, thanks to Stephen Clouse, we now have basic Oracle support in Slash 2.0 (in CVS). I've tagged it orapatch in MAIN. If it doesn't work, we can back out. I plan on installing the code on slashcode.com and use.perl.org tomorrow morning and we can give it a full-scale testing. The hope is to then, if it all goes well, release 2.0.0-pre2 tomorrow or Wednesday, and then let you all try to break it for a week before releasing 2.0.0. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Chris N. <pu...@po...> - 2001-04-23 15:42:21
|
Thanks Art, I found the problem, and will be committing a fix shortly. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Art G. <agi...@i-...> - 2001-04-23 14:56:02
|
Chris,
Actually, I've seen this behavior as well. I've been poking around the source and can't figure it out, but it definitely happens:
cp header;misc;default header;misc;art
<edit header;misc;art so that __section__ is now 'art' instead of 'default'>
template-tool -u slash -s header;misc;art
-> Preparing to insert header using filename header;misc;art
-> updated template header;misc;art tpid 4
Instead of creating a new entry in the db, it updates tpid '4'; the 'default' template.
I've tried using the -S art switch, too, but it always updates the existing template, instead of creating a new one.
Art
On Mon, Apr 23, 2001 at 10:31:23AM -0400, Chris Nandor wrote:
> At 10:00 +0200 2001.04.21, Alvaro del Castillo wrote:
> >On 20 Apr 2001 14:26:15 -0400, Chris Nandor wrote:
> >> At 19:31 +0200 2001.04.20, Alvaro del Castillo wrote:
> >> >I have spent some days to migrate our modified database to slash 2.0.
> >> >With the slash1toslash2 script all seems to be migrated well but in my
> >> >installation, Debian Potato, the version of MySQL 3.22.32 doesn't
> >> >support the MySQL command:
> >> >
> >> >CREATE newstories SELECT * FROM stories
> >>
> >> Ack. Well, realize two things:
> >>
> >> * Slash 2.2 will almost certainly require MySQL 3.23
> >> * Upgrading from 3.22 to 3.23 is very very easy (in my experience, and in
> >> the words of others)
> >
> >Ops, it's a pity. I, as a developer, can migrate easily to MySQL 3.23
> >but thinks in users who want to run slashcode but they must use it with
> >a distribution.
>
> I dunno. We asked several times on the lists and on the web site if anyone
> had a problem with going to 3.23, and not one person said they did, that I
> recall.
>
>
> >Actually, yo can use it with Debian Potato, a very
> >stable and widely used distribution.
>
> Yeah. Since packages and RPMs are available, and even upgrading from
> source is very easy AFAICT, those are all good signs.
>
>
> >The next stable version for Debian will appear in the end of this year I
> >think. But I can make some test and maybe we can generate Debian Potato
> >packages for this MySQL version.
>
> For Slash 2.0, yes. For Slash 2.2, it probably just won't work. You will
> almost surely need 3.23.
>
>
> >Yes, sure. Maybe the slash 2.2 version will be published when we have a
> >new version of Debian. And slashcode can't be limited for a
> >distribution. But we must work to make slashcode more and more easy to
> >use it with distributions and packages ;-)
>
> Well, at the very least, since Slash 2.0 will be finalized soon and will be
> stable and will get all the bugfixes and will work (does work) fine with
> MySQL 3.22, the worst case is we tell people to use Slash 2.0.x until their
> packages/dist are upgraded to use MySQL 3.23.
>
>
> >> >But there is a problem. The template-tool doesn't work right. When you
> >> >use: template-tool -s index;index;gnome it updates the
> >> >index;index;default !!! :-(
> >>
> >> template-tool gets its information not from the filename, but for the
> >> information embedded in the template. Chances are the section in the file
> >> is labelled "default". Please confirm that this is the case. Thanks,
> >
> >Nop, I know it. In the template I change the section to gnome. So the
> >template name was index;index;gnome and the section into the file was
> >gnome. And when I save it with "template-tool -u slash2 -s
> >index:index;gnome" the tool updates the index;index;defautl template.
>
> I have never seen this before, and don't know how it could be the case. In
> Slash::Install::readTemplateFromFile, it just does:
>
> for(qw| name page section lang seclev description title |) {
> chomp($val{$_}) if $val{$_};
> }
>
> And then in Slash::DB::setTemplate(), it just passes the data along.
>
> The only thing I can figure is that maybe you have some bad newlines (maybe
> some CRLFs instead of plain CRs, or maybe some extra spaces or other
> characters at the end of the __section__ line?) so that the section was not
> defined, which would make it default to "default".
>
> --
> Chris Nandor pu...@po... http://pudge.net/
> Open Source Development Network pu...@os... http://osdn.com/
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
---end quoted text---
|
|
From: Chris N. <pu...@po...> - 2001-04-23 14:32:39
|
At 10:00 +0200 2001.04.21, Alvaro del Castillo wrote:
>On 20 Apr 2001 14:26:15 -0400, Chris Nandor wrote:
>> At 19:31 +0200 2001.04.20, Alvaro del Castillo wrote:
>> >I have spent some days to migrate our modified database to slash 2.0.
>> >With the slash1toslash2 script all seems to be migrated well but in my
>> >installation, Debian Potato, the version of MySQL 3.22.32 doesn't
>> >support the MySQL command:
>> >
>> >CREATE newstories SELECT * FROM stories
>>
>> Ack. Well, realize two things:
>>
>> * Slash 2.2 will almost certainly require MySQL 3.23
>> * Upgrading from 3.22 to 3.23 is very very easy (in my experience, and in
>> the words of others)
>
>Ops, it's a pity. I, as a developer, can migrate easily to MySQL 3.23
>but thinks in users who want to run slashcode but they must use it with
>a distribution.
I dunno. We asked several times on the lists and on the web site if anyone
had a problem with going to 3.23, and not one person said they did, that I
recall.
>Actually, yo can use it with Debian Potato, a very
>stable and widely used distribution.
Yeah. Since packages and RPMs are available, and even upgrading from
source is very easy AFAICT, those are all good signs.
>The next stable version for Debian will appear in the end of this year I
>think. But I can make some test and maybe we can generate Debian Potato
>packages for this MySQL version.
For Slash 2.0, yes. For Slash 2.2, it probably just won't work. You will
almost surely need 3.23.
>Yes, sure. Maybe the slash 2.2 version will be published when we have a
>new version of Debian. And slashcode can't be limited for a
>distribution. But we must work to make slashcode more and more easy to
>use it with distributions and packages ;-)
Well, at the very least, since Slash 2.0 will be finalized soon and will be
stable and will get all the bugfixes and will work (does work) fine with
MySQL 3.22, the worst case is we tell people to use Slash 2.0.x until their
packages/dist are upgraded to use MySQL 3.23.
>> >But there is a problem. The template-tool doesn't work right. When you
>> >use: template-tool -s index;index;gnome it updates the
>> >index;index;default !!! :-(
>>
>> template-tool gets its information not from the filename, but for the
>> information embedded in the template. Chances are the section in the file
>> is labelled "default". Please confirm that this is the case. Thanks,
>
>Nop, I know it. In the template I change the section to gnome. So the
>template name was index;index;gnome and the section into the file was
>gnome. And when I save it with "template-tool -u slash2 -s
>index:index;gnome" the tool updates the index;index;defautl template.
I have never seen this before, and don't know how it could be the case. In
Slash::Install::readTemplateFromFile, it just does:
for(qw| name page section lang seclev description title |) {
chomp($val{$_}) if $val{$_};
}
And then in Slash::DB::setTemplate(), it just passes the data along.
The only thing I can figure is that maybe you have some bad newlines (maybe
some CRLFs instead of plain CRs, or maybe some extra spaces or other
characters at the end of the __section__ line?) so that the section was not
defined, which would make it default to "default".
--
Chris Nandor pu...@po... http://pudge.net/
Open Source Development Network pu...@os... http://osdn.com/
|
|
From: Stephen C. <the...@wa...> - 2001-04-23 08:04:55
|
I just finished a marathon session checking every method that wasn't
overriden yet to make sure it didn't need to be. (Guess what -- most of them
did). For better or for worse, here it is, as threatened yesterday.
1. Grab the latest CVS from SourceForge (this was diffed against it about ten
minutes ago).
2. Untgz the attached in your working directory.
3. patch -p0 < oraslash.patch
4. Pray and follow the INSTALL instructions.
As usual, no guarantees are offered. I can tell you it (mostly) works for me
and that's about it. There are still some issues with slashd but these stem
more from the way I installed Slash on my local box than anything
else. Theoretically it will work properly with a proper installation.
Note that this is an extremely brute force hack at the moment. The stuff for
placeholders has been in for a while but it's only used where necessary -- just
about everything is copied from the MySQL driver verbatim and changed where
appropriate. Deadlines are my excuse -- the 2.0 chopping block is being wheeled
out and I'd prefer to see some sentiment of Oracle support in there, even if it
sucks from a programmer's standpoint. I do intend to clean up as much as I can
before they decide to cut off submissions.
Anyway, try it out on Oracle, if you dare :)
--
Stephen Clouse <the...@wa...>
warpcore.org Founder, Chief Megalomaniac, and Evil Overlord
|
|
From: CertIndex.com W. <web...@ce...> - 2001-04-22 08:37:19
|
well naming a comment a thread is just as confusing as naming an article a thread. it still collides with the comment display mode 'threaded' i feel. i'm sorta at a loss. while it isn't super important which terms we use, we're putting a lot of work into this message board plugin and i'd like it to be good. proper / logical terminology helps usability and that's good. if i dont' come up with naything better in the next couple days, i'll just call them articles. maybe i'll prefix their uses with 'news' and 'message board' so you'd have 'news article' and 'message board article'. *shrug* whatever. i won't hold back this project for lack of better terms. if people like it they'll use it whether we have great terms or not i guess. :-) regards. ps: thanks all for your input ----- Original Message ----- From: "Ask Slashdot Guy" <cl...@sl...> To: <sla...@li...> Sent: Friday, 20 April, 2001 07:52 Subject: Re: [Slashcode-development] bulletin board input (Score: 5, Insightful) > Again I make the mistake of offering suggestions pre-caffeine: > > "Forum" > > Users create forums for their issues while regular authors can post: > > "Stories" > > And comments to each can be called: > > "Threads" > > ..without much confusion. > > > OK, off to get caffeine. > > - Cliff > > > On Thu, 19 Apr 2001 21:10:50 -0700, CertIndex.com Webmaster said: > > > how about 'message'? > > > > i just renamed all of the instances and so on to 'Message Board' anyway, for i think it's a > > trifle more modern than the throwback to our dial-up gathering places of yore. =) > > > > so you would post a message, then people would comment on the message. > > > > (however we're making a plugin for bender to allow webmessaging (NOT web-based IM's) so it may > > conflict.) > > > > *shrug* > > > > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development > |
|
From: Stephen C. <the...@wa...> - 2001-04-22 05:46:43
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, if that don't beat all -- comments work now. I came up with a little hack involving a global temporary table to allow me to turn a string into a CLOB for the duplicate comment checking function, and that was the biggest hangup. Speaking of CLOBs, I looked back at my schema and changed a bunch of places where I thought they were overkill -- tables like vars and such. Originally I had done a blind s/TEXT/CLOB/g when converting from the original MySQL schema, because CLOB was the only thing that matched TEXT (65535 characters). But a closer look revealed that the most likely reason TEXT was used on some of these fields is because the next step downward is TINYTEXT (255 character max), not nearly long enough. So I sanity checked all the CLOB instances and replaced most of them with VARCHAR2(4000), which should be plenty. Obviously CLOB remains for stuff like comment and story text. Tomorrow I'll be pulling things full circle, taking a look at the daemon stuff and those ugly red-headed stepchildren in Slash::DB::Static whose existence no one wants to acknowledge. I believe that's the last major piece of functionality left. With the addition of comments, the Web end of things is pretty much feature complete. Also tomorrow I'll supply a patch against the latest CVS for everything I've mangled so far, if any of you out there are daring enough to try it out. The main reason for the rushed release is so it can all get looked over for inclusion in 2.0. There is a lot here (the diff at present is 138K) and the changes to the core are significant enough that someone with more tenure needs to take a long look at them, and I've been told that it needs to happen quite soon (geez, this sounds like my day job :). However, I've been testing the code on both Oracle and MySQL and MySQL hasn't complained yet, so that's probably a good sign that it's stable. The unleashing commences tomorrow. Brace yourself. - -- Stephen Clouse <the...@wa...> warpcore.org Founder, Chief Megalomaniac, and Evil Overlord -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQA/AwUBOuJwQN1EXk7JbKbMEQKIGwCfZRswSq0IWh4TtlASg+nwQVMkxf0An0aL 8fEoBpZOslv02l5ILWpTx4tX =zzi3 -----END PGP SIGNATURE----- |
|
From: Alvaro d. C. <ac...@ba...> - 2001-04-21 08:10:15
|
On 20 Apr 2001 19:03:31 +0100, Dave Hodgkinson wrote: > Alvaro del Castillo <ac...@ba...> writes: > > > Hi! > > > > I have spent some days to migrate our modified database to slash 2.0. > > With the slash1toslash2 script all seems to be migrated well but in my > > installation, Debian Potato, the version of MySQL 3.22.32 doesn't > > support the MySQL command: > > If you can do it, I'd heartily recommend moving to MySQL 3.23. Just > all round better. Ok, I will take this suggestion and spent some time takeing a look at it ;-) Thanks -- Alvaro > > -- > Dave Hodgkinson, http://www.hodgkinson.org > Editor-in-chief, The Highway Star http://www.deep-purple.com > Interim CTO, web server farms, technical strategy > ---------------------------------------- > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development > |
|
From: Alvaro d. C. <ac...@ba...> - 2001-04-21 08:09:18
|
On 20 Apr 2001 14:26:15 -0400, Chris Nandor wrote: > At 19:31 +0200 2001.04.20, Alvaro del Castillo wrote: > >I have spent some days to migrate our modified database to slash 2.0. > >With the slash1toslash2 script all seems to be migrated well but in my > >installation, Debian Potato, the version of MySQL 3.22.32 doesn't > >support the MySQL command: > > > >CREATE newstories SELECT * FROM stories > > Ack. Well, realize two things: > > * Slash 2.2 will almost certainly require MySQL 3.23 > * Upgrading from 3.22 to 3.23 is very very easy (in my experience, and in > the words of others) Ops, it's a pity. I, as a developer, can migrate easily to MySQL 3.23 but thinks in users who want to run slashcode but they must use it with a distribution. Actually, yo can use it with Debian Potato, a very stable and widely used distribution. And we are working in making Debian packages for all the software needed to install slashcode-2.0 as a Debian package. I know that other people around slashcode are working in the same task. The next stable version for Debian will appear in the end of this year I think. But I can make some test and maybe we can generate Debian Potato packages for this MySQL version. > > Of course, if you are using Debian packages and don't want to change that, > you're kinda stuck until Debian comes out with a 3.23 package (which maybe > they have ... ?). Yes, sure. Maybe the slash 2.2 version will be published when we have a new version of Debian. And slashcode can't be limited for a distribution. But we must work to make slashcode more and more easy to use it with distributions and packages ;-) > > > >The solution is easy. Not destroy the table and use: > > > >INSERT INTO newstories SELECT * FROM stories > > That sounds OK to me. I'll look into it. > > > > >I am playing now with the templates and its customization for sections. > >It works quite well. It's fantastic to change the feel of a section > >creating a template for it. > > Yeah! I did a lot of the work setting up the template system, but even I > was kinda blown away when I first started using it to customize > http://use.perl.org/. I wanted a common copyright notice, so I created a > "useperlcopyright" template and put a few INCLUDE directives in the > templates, and boom! I really like the system we've come up with, it's > turned out better than I imagined, so far. Yes. In our slashcode modified, each user can have her own section. Think about it. Each user can control the templates for her section. We use ACLs for this. We are going to need a tool to edit the templates in the web and test the results ;-) > > > >But there is a problem. The template-tool doesn't work right. When you > >use: template-tool -s index;index;gnome it updates the > >index;index;default !!! :-( > > template-tool gets its information not from the filename, but for the > information embedded in the template. Chances are the section in the file > is labelled "default". Please confirm that this is the case. Thanks, Nop, I know it. In the template I change the section to gnome. So the template name was index;index;gnome and the section into the file was gnome. And when I save it with "template-tool -u slash2 -s index:index;gnome" the tool updates the index;index;defautl template. I have said it, you guys have done great work with slashcode. Bye -- Alvaro > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development > |
|
From: Chris N. <pu...@po...> - 2001-04-20 18:27:35
|
At 19:31 +0200 2001.04.20, Alvaro del Castillo wrote: >I have spent some days to migrate our modified database to slash 2.0. >With the slash1toslash2 script all seems to be migrated well but in my >installation, Debian Potato, the version of MySQL 3.22.32 doesn't >support the MySQL command: > >CREATE newstories SELECT * FROM stories Ack. Well, realize two things: * Slash 2.2 will almost certainly require MySQL 3.23 * Upgrading from 3.22 to 3.23 is very very easy (in my experience, and in the words of others) Of course, if you are using Debian packages and don't want to change that, you're kinda stuck until Debian comes out with a 3.23 package (which maybe they have ... ?). >The solution is easy. Not destroy the table and use: > >INSERT INTO newstories SELECT * FROM stories That sounds OK to me. I'll look into it. >I am playing now with the templates and its customization for sections. >It works quite well. It's fantastic to change the feel of a section >creating a template for it. Yeah! I did a lot of the work setting up the template system, but even I was kinda blown away when I first started using it to customize http://use.perl.org/. I wanted a common copyright notice, so I created a "useperlcopyright" template and put a few INCLUDE directives in the templates, and boom! I really like the system we've come up with, it's turned out better than I imagined, so far. >But there is a problem. The template-tool doesn't work right. When you >use: template-tool -s index;index;gnome it updates the >index;index;default !!! :-( template-tool gets its information not from the filename, but for the information embedded in the template. Chances are the section in the file is labelled "default". Please confirm that this is the case. Thanks, -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Dave H. <da...@ho...> - 2001-04-20 18:11:09
|
Alvaro del Castillo <ac...@ba...> writes: > Hi! > > I have spent some days to migrate our modified database to slash 2.0. > With the slash1toslash2 script all seems to be migrated well but in my > installation, Debian Potato, the version of MySQL 3.22.32 doesn't > support the MySQL command: If you can do it, I'd heartily recommend moving to MySQL 3.23. Just all round better. -- Dave Hodgkinson, http://www.hodgkinson.org Editor-in-chief, The Highway Star http://www.deep-purple.com Interim CTO, web server farms, technical strategy ---------------------------------------- |
|
From: Alvaro d. C. <ac...@ba...> - 2001-04-20 17:58:22
|
Hi! I have spent some days to migrate our modified database to slash 2.0. With the slash1toslash2 script all seems to be migrated well but in my installation, Debian Potato, the version of MySQL 3.22.32 doesn't support the MySQL command: CREATE newstories SELECT * FROM stories The solution is easy. Not destroy the table and use: INSERT INTO newstories SELECT * FROM stories I am playing now with the templates and its customization for sections. It works quite well. It's fantastic to change the feel of a section creating a template for it. I have created index;index;gnome for example and it controls now the HTML rendering of the index for this section. But there is a problem. The template-tool doesn't work right. When you use: template-tool -s index;index;gnome it updates the index;index;default !!! :-( The solution for now is to save another time index;index;default. This time template-tool creates a new template for it :-) I have no time now to do the bug report and publish a patch. Maybe tomorrow when I continue the great playing. Have a good weekend ;-) -- Alvaro |
|
From: Eric D. <eri...@ja...> - 2001-04-20 17:13:11
|
Yeah, thats a good idea Ask Slashdot Guy wrote: > Again I make the mistake of offering suggestions pre-caffeine: > > "Forum" > > Users create forums for their issues while regular authors can post: > > "Stories" > > And comments to each can be called: > > "Threads" > > ..without much confusion. > > OK, off to get caffeine. > > - Cliff > > On Thu, 19 Apr 2001 21:10:50 -0700, CertIndex.com Webmaster said: > > > how about 'message'? > > > > i just renamed all of the instances and so on to 'Message Board' anyway, for i think it's a > > trifle more modern than the throwback to our dial-up gathering places of yore. =) > > > > so you would post a message, then people would comment on the message. > > > > (however we're making a plugin for bender to allow webmessaging (NOT web-based IM's) so it may > > conflict.) > > > > *shrug* > > > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development -- Back up my hard disk? I can't find the reverse switch! Eric Dannewitz - Adventurer, saxophonist, good-timer (crook? quite possibly), clarinetist, manic self-publicist, part-time flautist(flutist?), macintosher, and often thought to be completely out to lunch. http://www.jazz-sax.com |
|
From: Chris N. <pu...@po...> - 2001-04-20 16:41:29
|
At 12:29 -0400 2001.04.20, Chris Nandor wrote: >Again, I need patches. I cannot comment on the usability of the code until >I see it. And if you want it in Slash 2.0, it needs to be done ASAP. Sorry, by "ASAP" I don't mean to rush it for today or anything, but early next week would be best. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Chris N. <pu...@po...> - 2001-04-20 16:30:10
|
At 00:15 -0500 2001.04.20, Stephen Clouse wrote: >reason. I dug up this comment in Slash::Apache::User: > >#Ok, this solves the annoying issue of not having true OOP in perl Well, that is one man's opinion, anyway. :-) ># You can comment this out if you want if you only use one database type ># long term, it might be nice to create new classes for each slashdb ># object, and set @ISA for each class, or make each other class inherit ># from Slash::DB instead of vice versa ... > >Perl's interface inheritance is definitely a "bottom-up" approach along the >lines of Eiffel, so trying to force the downward inheritance into Slash::DB >itself doesn't work very well. So today I fixed that, flipping the current >"top-down" model over. IMO Slash::DB just got a hell of a lot simpler -- all Well, we have been considering ways to change it anyway. I am not sure what you mean when you describe how you changes it though. That is: >it >does is figures out the correct class name, loads the necessary driver module, >and then blesses the initial hash into that class instead of Slash::DB. The >onus for proper inheritance is now placed on the database driver module, which >is probably a Good Thing. I've already patched all the existing drivers and How does the database driver module determine inheritance? Do you mean that now you get back a Slash::DB::MySQL object instead of a Slash::DB object? >I've also tightened up Slash::DB::Utility some more, breaking out select >statement generation into an independent function, as well as reusing >some of the sql functions inside the sql functions when possible. This >eliminates copious amounts of redundancy in the sqlSelect* routines. >MySQL code >continues to work in its original form (I haven't gotten around to >modifying any >of it yet), so I'd have to say the extended interface has proven itself clean >and backwards-compatible. Again, I need patches. I cannot comment on the usability of the code until I see it. And if you want it in Slash 2.0, it needs to be done ASAP. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
