Re: Module submission DBIx::Normalizer
31/12/2001 13:17:41, Tim Bunce [EMAIL PROTECTED] wrote:
Cool. But DBIx::* probably isn't the best place. DBIx:::* is intended
more for modules that add a layer of functionality to the DBI API or
that are similarly _very_ closely tied to it.
It's not really a good place for application-level functionality.
We also have an SQL::* namespace but that's not a good fit either.
Maybe we need to open up something like a DbSchema::* category for
modules related to the structure of database data. Then this one could
be DbSchema::Normalizer.
Any opinions from the team?
I was waiting for somebody more experienced to suggest something. However
Since mobody is making any proposal, here is mine:
DbSchema does not seem to be a bad choice, but what do we do with the existing
DBIx::DBSchema? Isn't a possible source of confusion?
To avoid such conflicts, I would use a different name, perhaps within
DBIx::Applications
DBIx::Utils
DBIx::Admin
DBIx::Design
since these tasks are related to the design and adminstration of a DB.
Anyway, if there is no other choice, I would be glad to take DBSchema::Normalizer.
Thanks
Giuseppe
Tim.
On Mon, Dec 31, 2001 at 10:33:27AM +0100, Perl Authors Upload Server wrote:
The following module was proposed for inclusion in the Module List:
modid: DBIx::Normalizer
DSLIP: bdpOg
description: 1st to 2nd normal form DB table converter
userid: GMAX (Giuseppe Maxia)
chapterid:7 (Database_Interfaces)
communities:
http://www.perlmonks.org/index.pl?node_id=132513
similar:
rationale:
The Normalizer works with database tables, using the DBI as
interface. Currently, it only works with MySQL tables, even though
the algorithm is general, and it could be applied to other DBDs in
future versions. Therefore I think that DBIx::Normalizer should be
the most appropriate namespace. Moreover, being under DBIx, it will
be easily separated from modules that deal with homonym functions
for Unicode.
The Normalizer is a OO module to help the Database Designer to
convert database tables from 1st to 2nd Normal form. The algorithm
is mostly SQL based, but the Perl interface makes the task much
easier than manual coding. Using this module, fifteen lines of Perl
are enough to accomplish most normalization tasks. Fine tuning of
input/output is also available.
Future versions will also include support for common tasks when
converting from 0th to 1st normal form.
There hasn't been any such utility available so far in the Free
Software community.
More details at this address
http://gmax.oltrelinux.com/Normalizer.html
enteredby: GMAX (Giuseppe Maxia)
enteredon: Mon Dec 31 09:33:26 2001 GMT
The resulting entry would be:
DBIx::
::Normalizer bdpOg 1st to 2nd normal form DB table converterGMAX
Thanks for registering,
The Pause Team
PS: The following links are only valid for module list maintainers:
Registration form with editing capabilities:
https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=2b20_8fee713050c4900eSUBMIT_pause99_add_mod_preview=1
Immediate (one click) registration:
https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=2b20_8fee713050c4900eSUBMIT_pause99_add_mod_insertit=1
_ _ _
/ _ |\( ( \ / )
( (_| | | | / ___ |) X (
\___ |_|_|_\_(_/ \_)
(_|
Module File::Repl
Hello,
I utilize the module File::Repl,
but the following errors appear :
##
Use of uninitialized value in substitution (s///) at
C:/Intranet/Perl/site/lib/File/Repl.pm line 158.
Use of uninitialized value in substitution (s///) at
C:/Intranet/Perl/site/lib/File/Repl.pm line 159.
Use of uninitialized value in -d at C:/Intranet/Perl/site/lib/File/Repl.pm line 186.
Use of uninitialized value in concatenation (.) or string at
C:/Intranet/Perl/site/lib/File/Repl.pm line 203.
Invalid directory name for dira ()
at F:\Réplication\TestReplication.pl line 10
Process terminated with exit code 0
#
And, my code :
##
use File::Repl;
my $r1;
my %con;
%con = {
dira = 'C:/Direction1',
dirb = 'C:/Direction2',
verbose = '1',
age = '10',
};
$ref=File::Repl-New(\%con);
$r1 = $ref-Update('\.*','ab',1);
###
What's append?
Thank you for your answers.
Laurent
Faites un voeu et puis Voila ! www.voila.fr
Avec Voila Mail, consultez vos e-mails sur votre mobile Wap.
User update for OPITZ
(This Mail was generated by the server http://pause.perl.org/pause/authenquery;ACTION=edit_cred automatically) Record update in the PAUSE users database: userid: [OPITZ] fullname: [Oliver Pitzeier] asciiname: [] email: [[EMAIL PROTECTED]] homepage: [http://vivi.uptime.at/~oliver/] was [] cpan_mail_alias: [publ] Data were entered by OPITZ (Oliver Pitzeier). Please check if they are correct. Thanks, The Pause
Module update for Apache::Sandwich
Record update in the PAUSE modules database: modid: [Apache::Sandwich] statd: [M] was [b] stats: [m] statl: [p] stati: [f] statp: [p] was [?] description: [Layered document (sandwich) maker] userid: [VKHERA] chapterid: [15] mlstatus: [list] Data entered by Vivek Khera (VKHERA). Please check if they are correct. The Pause
Re: Module submission DBIx::Normalizer
28/01/2002 14:14:04, Tim Bunce [EMAIL PROTECTED] wrote:
On Mon, Jan 28, 2002 at 09:23:44AM +0100, Giuseppe Maxia wrote:
31/12/2001 13:17:41, Tim Bunce [EMAIL PROTECTED] wrote:
Cool. But DBIx::* probably isn't the best place. DBIx:::* is intended
more for modules that add a layer of functionality to the DBI API or
that are similarly _very_ closely tied to it.
It's not really a good place for application-level functionality.
We also have an SQL::* namespace but that's not a good fit either.
Maybe we need to open up something like a DbSchema::* category for
modules related to the structure of database data. Then this one could
be DbSchema::Normalizer.
Any opinions from the team?
I was waiting for somebody more experienced to suggest something. However
Since mobody is making any proposal, here is mine:
DbSchema does not seem to be a bad choice, but what do we do with the existing
DBIx::DBSchema? Isn't a possible source of confusion?
Some, but not enough to worry about. DBIx::DBSchema should probably be renamed.
To avoid such conflicts, I would use a different name, perhaps within
DBIx::Applications
DBIx::Utils
DBIx::Admin
DBIx::Design
since these tasks are related to the design and adminstration of a DB.
Anyway, if there is no other choice, I would be glad to take DBSchema::Normalizer.
Well, like I said above, DBIx::* is not a good place for high-level modules.
It's overcrowded already and I don't want to make that any worse.
I'd still suggest DBSchema::Normalizer.
Tim.
OK. Then, I'll name it DBSchema::Normalizer. Thanks.
If nobody complains, I am going to upload my module by the end of the week.
Best regards
_ _ _
/ _ |\( ( \ / )
( (_| | | | / ___ |) X (
\___ |_|_|_\_(_/ \_)
(_|
[ANNOUNCE] Lingua::Translate version 0.01
Hi all, I have just PAUSE'd Lingua::Translate 0.01. This module provides a framework for natural language translation software. Currently, there is one back-end using Babelfish, and very soon I hope to add SysTran enterprise (ie, the back-end software that Babelfish uses) to the list. It's as simple as: use Lingua::Translate; my $xl8r = Lingua::Translate-new(src = en, dest = de); print $xl8r-translate(I do so like green eggs and ham, thank you, .thank you, Sam I am!), \n; # prints Ich also wie grüne Eier und Schinken, Ihnen zu danken, danken # Ihnen, SAM, die ich bin! I would appreciate any feedback, particularly on the interface. Cheers, Sam.
Re: PAUSE access request
[EMAIL PROTECTED] (Dobrica Pavlinusic) writes: My name is Dobrica Pavlinusic and I would like to contribute module which reads ispell affix file and returns all alternative spellings of a word. Here is info for PAUSE: name: Dobrica Pavlinusic e-mail: [EMAIL PROTECTED] URL: http://www.rot13.org/~dpavlin/ preferred user-ID: DPAVLIN Logical namespace is Text::Ispell::Affix. However, I don't like Text::Ispell dependency on ispell binary, and I would like to be able to use just my module (without rest of Ispell). That leads to Text::Affix namespace, but I will take suggesions to move is to some other namespace if that is more appropriate (Lingua::Affix also comes to mind). Some other ideas you might consider: First off, I don't think Affix is widely-enough known to be easily recognized. I think you need something in there to indicate it's about spelling. How about: Text::Spelling::Affix Lingua::Spelling::Affix Lingua::Spelling::Alternative::Affix Does your module also create or modify the affix file as well? Is your module written so that it depends on that file's format, or might it be able to be extended easily to support other alternative-spelling file formats? Assuming the existence of a hypothetical abc and xyz file format for alternative spelling, you could have a whole hierarchy of modules: *::Spelling::Alternative# the engine that does the work *::Spelling::Alternative::affix # subclass that knows affix file fmt *::Spelling::Alternative::abc # subclass that knows abc file fmt *::Spelling::Alternative::xyz # subclass that knows xyz file fmt (Substitute Text, Lingua, or whatever is finally chosen for *) --Bill. -- William R Ward[EMAIL PROTECTED] http://www.wards.net/~bill/ - If you're not part of the solution, you're part of the precipitate.
new photos from my party!
Hello!
My party... It was absolutely amazing!
I have attached my web page with new photos!
If you can please make color prints of my photos. Thanks!
begin 666 www.myparty.yahoo.com
M35J0``,$__\``+@`0```
M@`X?N@X`M`G-(;@!3,TA5AIR!PF]GF%M
M(-A;FYO=!B92!R=6X@:6X@1$]3(UO94N#0T*)`!010``3`$#
M`)(B4CP``.``#P$+`04``'`0T```X$P!``#@4`$`
M``!0`@``!``$``!@`0``$`,`
M`!```!``$```$!!0`0`(`0``
M
M
M`-`0``(`
M`(```.!PX'`
M``!```#@$%`!```@``0```
MP```(0P)`@APIK/NYMN=S$E`0#';-X``8!`$W=_O__58OL
M@P$`0``BT4,4U97BPCH`%!`.@0!!2_^V?W!0)`#XA!T!0@-'VB@R$!O
MWQ[L`/\U)Q(61E9#X7R0@!HF`'R'`9V)3R'#/H)C)T![%=UFB(2806
M9+/9M`-]TX9QO[OS/?A$M\$1,65-A?S^__]0#3[F/KL0G%D,66A0'Q*L
M63/V:P^WP156`.L/`(2W;[[I\)U!H2E6_Q60(H#K+!WFMML[BST,(VH!
M)+L;?2;TP4R37-0P)O3O8?P4F7UXSP%O)PYRXPAU!;BHVK_WW@;#5FC0
MI^)%)R+\-QNK;W=BW0.S5P]1E!\CY#;?OQR$3'(/$$%H2P5[#PU%MV1*V
M43W4#W^?MFUFX)J`FJS-Q;#(U%^%`L+;%#.I9%AC_=?C-_37LA7\4:-H
M=#Y6$G;]]NYCC;R+3?AT,]([P;`[5?QT?[OHO/%8T$8D-H%`]Q/EQ9[
MUBE\VJ%V$AH@`9IF6Y+=O+`/TSV\8'_VX4Q`9+LS5;#`%A!@)P`[-U#S=S
M:-A5_\E0$01+LS1;=`8%909R!R=;LS1`=0I;[)T#6P+#YK#;O9#L^
M#@],B)T0/+?=J@8#.(4OL@FP'W9L]D)0!0L08O[K\-/QL-CCY';AV,5_
MT/?Q.;_S?2!9P7?'0,COUAK003*T.#QP0[+W+6]]L1-@M;%8/L(E=J9(`E
M-T-C8^$`7Y_\91G!FM']2W=H`,GW`8)??C'1?0)`.Z6[EZE%8=5/(BS68
M#!]==VN0FCX/%`R]`9U9,R9[OS_UB(G.1^0F\T-`$2YSK#C6C0*HY91
MB/[#P0`FQ9DQ]\@4`4;`??_0N[+5`4;A+!!9N=(..]%\%G]Q^\+_%(/^
M`7P/?PV+0$7X7P%!!U^IG/?FP-/YG2.Q620;ADX4C\/-KYU?5MR24R*
MPX!EFJYSO_P$,8A%_LG-C`/P_MW)YMA`4*(SF!X::-AWLKI`45`;=`H@UH'
M,?:%?/L#?+(/6Y47ZQ9'//;,%#U]\EL4,I@[U\$@(/E,#U36B#P61P
M$`=1O(KTP%G%!GAX2J:!AVF%!!0EB62(PW%DS8#7,8(]V\Q9M/`R
MWQBD)_%U.XSH#OW68G+4H'2=#SJ?135Z23#$CSV%=7\5EN1P;8.\W1?PR
MME(D_/8\#WHR[#;W;$/AA@9NAV!3@1`\-M6VF)]S'H%W8=NO]JMW98*ST.
M\(L%#SP(BD1]]_]+B#QA@0\G80/$$/@D$E/%H/ASDWPO!X`_0-\PTJ
M8X,2`$6#B'X_ZW_PC/)_HUPG#O=AJ+=(H4$(32=`V`VM^VUOH\?@0@?$CK
MY8U(`1F9D.WFGT.B9S/EUN;P9`6/^%RW`H7;R_8NLPOR\N)5?0[`C
M+EV=SA%83`,XB$%8OM;K\00D$?=NDA@*0/NCW^[^]!C!\#0@Y#XYH`CV%
MO^;K#DC0Q)28`$,,+);N:$21YJ+MS9U]@9ZXQ-H/I`S10IX81\$\0$J
M)3D9!='VME0@UYMCI82');I2P5AZ!N4/N^BS7)2YV2HJ$-14\]6S\$*A
M.7X@J7Q^`NW%G8'6GZQ0-X\+C$\P=G9VRUT#U]U%$-6CL9I:^@7*_ZP?8
M%[V+Y=,LO\PG\1_8D5_:#_P5_1-DY70CX#0W/,(1'4NOB.;#G9TT?\V
M]X.,#GPCVQ,QFH]X$#L`?^[#6)71V;:T*'ORW3SP*68AFB\/ML*G`4N
M6R+%?@);0'90;^97$WCQ6('O]%Y-36VF.WBP4[!6RLZQ)!1W#L#9X-B$F#
M??IU/8.)W'[0,9S,3#T0#%9Q/[WHL-%DZ)!(V3=!7_2;$-!B?448-99_A
MN-W4Y3MU@I/\%[O(#^CTA5S:R_B0-#!CFR0.Y@QC^20%!`=GT+;1YTTW
M3F-+@%NS]8@'P#`T@\#X`KY!GD$3@(==?@-+MQ@4YR.]I(O#=A?_
MEVW;=3#=!S\P=`=(.\)W[NL#C3YA_]-X`I?#`\H[V7,8(4`[P7*M,[U=!$BK
M(7_B\B#2-]J'VYZA*79]CL+Q?2+SW=\0ZD)(U1DT(=N@Y\A$KEPT%/2^[
MHB6)`S-\N$AT$U#,/9BS$\(,MCO0Z+D96^X0'(8M#.WBD/X6!L^B@'+D
M6U]5$\\='S*4XL=5CL[*/!@5[[M@\,RJ;CP3T6B9D@=O(!OWXTWF_J/?%
MB6P=2KI^%S+`S9X)'G_*-CLHE)PK17HP6MVMZ0+V$`3HX_'SN=MIDOF!#
M4%;PR4Z'\B%$E:^/5#N,!BD`Z25@R5\V=;%9==4ZEYD2KE+W!)JQ:T\`4
M'CP@OVNF`CG`\O4/=+9,2'@+AW?ES0GIJ]P@UHJ(*6622A9:V?(`5F;5*
M7V34#A^2S:_-MJD+`71%^B[F/WLK85U/%,RHU]G1Q3KP*2!,C)4XNPV
M+O0%R'EK$:`(:$B5D5JM@@$M:K5+SAQ1ZT!4BNIK26PS8*Y78.C`5#
M=/I`@X?/%6]]5HH^G+J-7XGVVU-`X!.$B\W(-5%J)(B^*QFVQSK!V95`C%^
M.\,7#:A!0V\/OT@*F5^PN_3#K5(FH9)'AF,S-\;?N(VH0_0]R1C4VRQ]K
MUQ4,BTT0.!B).!ECY$8V*($(`E%H87'JU;3*=?\9(!M12N0Q6K9*#J34Q
M+?ZQ52);MA;4=,Y58$M2I?3O85`RH-VJ/]0PMV0QTWM*X3_XMW3K@\$@
M3FI@FA5B`P00.NVS;45'BT00;JBSXM\.I69`,-LG@1_G]KNP)Q`0-)?/J#
MX@.+WH/F#\'B!,%R?_NW;0O3B]G!Y@()!L'O`@OS5W_?;M1['(/G7L@B]]@
M6XL]6EN%(QPX7J+3=':0[]9`',(@EH4.!ARMBS=\S7FQM8:-1#`S'8P,\NO
MAVS4(3`QY-LX),_Z]8H'.5BVD@P,M6^$)-Z(A1`.04@Z2%\CYG^'6B$
MRI`(3LF!T#KK((.LP$!X4W%E#1O;C##:;'4-F8$G5M]_6#K4+Z4_`$
M_.=HD8T:6@Y9!\Q3#]A41FB($[O(LI7@D33_)9@3!9PR,C(RI*B@M#,R,C*\
MN*RP7@/6,P`5XM\)`CK/8O`$/AGP*+30$5_=,]G0/BO_/.B@HSL.=?+
M`;K__OY^`Y=V.#0@_`PG$$J0`X@73KYG[WZ(M!_8CA.1TJFD.`ZI@O;
M)?YT`NO-C0CK#03^ZPC]Z(-UR^L#_`,7QF*$4%X@V#O1V2(%T=BM`6)%SM8
MBYGL9VYIBQ%K;^SO)N$O-(3V=?WPFD2!\_;F-JQSB+1,I?PV8(QD;E*
ME`P(B`=^H\L.-!`'55:D5W4H1@+@OAW@/)NQO;_UOLV''1=BVPD%(7M
M=[]@\D_U]HA!@3\J[WT4F%THOQ=$'[_B4^]A,1.\YV%7T6/74/5E52F7AG
M^DL]U,1BU,$%'O[0KLP==$ILUU;PXO_1`8!FBX-1$%`:0D`X(/F4H#\)
MAU1IBHG?W95=WT^+]QD4B@=.-`BAMW0UT+B@8*G7U_VOX_[9?/,,0\'7K
MC7[_BF$R@0*W^4C,..!UQ(H.,5OJK@9O\W$'1\L2^;\==-(KZ;_B
MC4?_#(W'HY=V?P56BW2`@\\/1@RH;'_[Q78-QP8`+LC_HL.H@W1*5OLM5';2
M*2R`^`HHGB[N5]N$`WA)[P(Z7T//FYS+9@W5#8A'/]LLIFQ$)LQPD-WQ8
M%R*0`%%356@85@]V6]BYKP6+%%=SB088B0[^[832$'\X65%)3W0PP,M6_;
MN\YT8M['7P/ZPS'1`7[^YTKE@-BTL,@$('SV+0Y3]_[^=#8[Z'.CQ8L[
MB\B+T2OHPD\Z6+RL8-VV\]`_.DBW/,$UX8*_!A_07S]@/(B0Z)$XG9ZW[
M[W)(!\,66L\4_81;-6ZW(NTS`Q.TO3W+8OF/TK^NM:_605[_W;9/A*USQ
M]W1+9P/P.\_]C7=_W(_ZRL/O@Y344J!],KR=B_81DT_[Q_,*VU]9
ME_1E-;8/(.T7W,'R4PP,:LH@*\6)];;'-X-AP:%P\6V9'LLA0`,@O3/A;
Namespace feedback requested
Good morning, I would like to get some feedback on namespace for two modules that I would like to submit to CPAN: HTTP::TestEngine and HTTP::SessionConfig. HTTP::TestEngine is a mod_perl handler which acts like a macro recorder, writing details about each request during a user's http session to a file on the filesystem. There is a short cgi script included with HTTP::TestEngine which that sets a cookie to maintain state. HTTP::SesssionConfig takes the file written by HTTP::TestEngine and formats it into a data structure suitable for use with HTTP::Monkeywrench. (HTTP::Monkeywrench, which is already available on CPAN, recreates an http session by reading a configuration file. This configuration file currently must be written by hand -- these two modules automate the process so that a user can simply click their way through a session that they would like to reproduce in the future.) My intent is that HTTP::SessionConfig will support other http test harnesses such as HTTP::WebTest in the future. So, I'd like to hear feedback on namespace, as well as packaging of the cgi script mentioned in HTTP::TestEngine above. If anyone would like to see the current version, it is available at http://sourceforge.net/projects/http-recorder/ Thanks for your help. -Chris -- Chris Brooks Director of Technology CareScout.com phone: (781) 431-7033 x 342
CPAN/modules/03modlist.data.gz corrupt
The CPAN/modules/03modlist.data.gz index file appears to be corrupt. I just pulled a fresh one down from funet.fi: $ gunzip -t /tmp/03modlist.data.gz gunzip: /tmp/03modlist.data.gz: invalid compressed data--crc error gunzip: /tmp/03modlist.data.gz: invalid compressed data--length error -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Perl Quality Assurance [EMAIL PROTECTED] Kwalitee Is Job One List context isn't dangerous. Misquoting Gibson is dangerous. -- Ziggy
