You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
(103) |
Apr
(37) |
May
(45) |
Jun
(49) |
Jul
(55) |
Aug
(11) |
Sep
(47) |
Oct
(55) |
Nov
(47) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(43) |
Feb
(85) |
Mar
(121) |
Apr
(37) |
May
(33) |
Jun
(33) |
Jul
(14) |
Aug
(34) |
Sep
(58) |
Oct
(68) |
Nov
(31) |
Dec
(9) |
2004 |
Jan
(13) |
Feb
(57) |
Mar
(37) |
Apr
(26) |
May
(57) |
Jun
(14) |
Jul
(8) |
Aug
(12) |
Sep
(32) |
Oct
(10) |
Nov
(7) |
Dec
(12) |
2005 |
Jan
(8) |
Feb
(25) |
Mar
(50) |
Apr
(20) |
May
(32) |
Jun
(20) |
Jul
(83) |
Aug
(25) |
Sep
(17) |
Oct
(14) |
Nov
(32) |
Dec
(27) |
2006 |
Jan
(24) |
Feb
(15) |
Mar
(46) |
Apr
(5) |
May
(6) |
Jun
(9) |
Jul
(12) |
Aug
(5) |
Sep
(7) |
Oct
(7) |
Nov
(4) |
Dec
(5) |
2007 |
Jan
(4) |
Feb
(1) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(22) |
Dec
(19) |
2008 |
Jan
(94) |
Feb
(19) |
Mar
(32) |
Apr
(46) |
May
(20) |
Jun
(10) |
Jul
(11) |
Aug
(20) |
Sep
(16) |
Oct
(12) |
Nov
(13) |
Dec
|
2009 |
Jan
|
Feb
(9) |
Mar
(37) |
Apr
(65) |
May
(15) |
Jun
|
Jul
(24) |
Aug
(1) |
Sep
(8) |
Oct
(4) |
Nov
(21) |
Dec
(5) |
2010 |
Jan
(35) |
Feb
(6) |
Mar
(8) |
Apr
|
May
(4) |
Jun
(3) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Charlie S. <Sm...@ld...> - 2003-11-19 19:01:23
|
I got an email saying that this message I'm trying to send to the group wen= t= over the 40KB limit, so I'll break it up. This is the first of two. = You'll need to use MS Word or something like that - maybe Codewrite - to = open the files, unless you can get them to a UNIX (preferred) box. Attached: SQL files used to create Oracle schema for phpesp. >>> "Charlie Smith" <Sm...@ld...> 11/18/03 10:00AM >>> Let's make all mysql declarations of 'NOT NULL default ', become NULL by = definition. It appears that Oracle will have to be dealt with in the at = the code level when dealing with the mysql empty string. We may be able to= = abstract this to by passing the query statement through some type of parser= ,= but I'm not sure how clean this would be. So far, it looks like we've got Stephan, Sean and Jeremy Buchman who have = volunteered on this project. I'll try and get the schema for Oracle in m= y= next email to you all. This should firm up the datbase design for the = Oracle schema. =20 I'm thinking that by using the PEAR DB library, those wanting to stay with = mysql could just substitute the PEAR DB calls in your unit testing, as you = go. So, whether using PEAR DB in some calls and direct mysql calls in = others, it should work. I've attached oracleIncBeta.php, the Oracle versions for all the mysql = calls I have identified as being used in the phpESP. Most were pretty = straigt-forward to handle. There was one that I'd like to see if we can = dispose of, however. See if you can guess which one it is. =20 Please take a look at these routines (there mysql counterpart would be = mysql_connect for oracleConnect, mysql_close for oracleClose, etc.) and = assist in identfying the PEAR DB function that would take it's place. I'd like to propose we use ORACLE as the test platform. Or at least, I'd = like to see the end product work with Oracle as one of the standard databases. I'll attach the Oracle schema in my next = posting. There are 13 functions. If you would like to sign up for one, please mark = your name or initials next to the routine. Please list the name of the identical PEAR DB fuction, if there is on. If = not please indicate. Mark TESTED with an 'x/ORACLE' to show test complete on Oracle platform. Mark INIT with your initials and then add a date when test complete. ex. = cws. ex. cws-11/18/03=20 =66unction PEAR DB = = TESTED/Platform INIT/Date =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D=3D=3D oracleConnect oracleClose oracleQuery oracleFetchArray oracleNumRows oracleExecuteQuery oracleFetchRow oracleError() oracleFreeResult oracleInsertId oracleResult oracleSelectDB oracleAffectedRows Charlie 11/18/03 Charlie Smith wrote on 10/24/03 10:26AM: <snip> Calling for help - W O U L D A N Y O N E B E INTERESTED = IN ASSISTING WITH THE PORT OF MYSQL TO PEAR DB? If so, please respond, and I'll try and divy out= = assignments. </snip> >>> "Charlie Smith" <Sm...@ld...> 10/06/03 07:28AM >>> So code would be modified to be: if (mystring=3D=3D'') mysql=3D'select * from designer where username is null'; else mysql=3D'select * from designer where username =3D ' + = quotefunc(mystring); See = http://www.tek-tips.com/viewthread.cfm?spid=3D759&newpid=3D759&sqid=3D65748= 0= for further discussion on topic of empty string. >>> "Charlie Smith" <Sm...@ld...> 10/02/03 01:51PM >>> Yes, the use of PEARDB should make the long if's largely unnecessary. =46or field definitions, I'd be inclined to go with NULLs as well. We'd us= e= the NULL and NOT NULL qualifier in the field definitions and work out the = default values in the code. So we'd keep fields defined as NOT NULL in = Oracle. The field definition of fieldname ... NOT NULL default '' is not= = valid in Oracle. Also, in Oracle, NULL fields are detected differently = that fields with data in them when using a select statement. ie. select * = =66rom table where field IS null=20 would be the code for going against the Oracle table rather than select *= = =66rom table where field =3D null (This is an invalid select as you have= = to use 'is' and 'is not' null when detecting null fields in the oracle = tables, not =3D and !=3D. So if there is code in phpESP which references = empty string in select statements, it would need to be modified. I had thought we may want to replace the NOT NULL default '' with just = default ' '. But had my reservations. Thanks for your input on this, = though I confess I am still a bit confused. In Oracle if there is no = supplied value for a nullable field (any field not declared as NOT NULL), = it's value is NULL by default. If you had a choice between default NULL an= d= NOT NULL, which would you want to go with? =20 =46or following fields we could translate to Oracle as follows? MySQL becomes Oracle int(10) unsigned NOT NULL default '0' NOT NULL default NULL, NULL int(10) unsigned default '0' default 0 enum('Y','N') NOT NULL default 'N' NOT NULL (with check constraint= = *) NOT NULL default '' NOT NULL * check constraint syntax: alter table designer add constraint designer_pdesign_ck check (pdesign in ('Y','N')); We could also put a trigger on the table/field so that on insert or update,= = if the new field value were null, it would get populated with 'N'. We = could handle all the other default values this way except for the empty = string ''. We'd have to modify the code for this where it selects from = table where field =3D ''. =46or ENUM types, a check constraint can be used in Oracle, to make sure = values are matched against those we want to allow. What would the syntax look like in PostGres? Does this sound agreeable? >>> "James E. Flemer" <jf...@uv...> 10/01/03 06:43PM >>> Jeremy Buchmann wrote: > On Wednesday, October 1, 2003, at 02:13 PM, Stefan Champailler wrote: >=20 >>> With that: >>> Let's discuss how to handle the schemas >>> 1) ENUM type in PostGreSQL and Oracle. >>> 2) the empty string in default values >>> 3) default values vs NOT NULL >> >> >> My Oracle and PostgreSQL is limited, so I ask the question : are we=20 >> planning >> to make severeal schema with the hope to have minimum code rewrite on the >> phpESP side ? (I guess it makes sense). >> >=20 > I think it's best to work out a schema that: >=20 > 1. Is as generic as possible so we can avoid or minimize code like this: >=20 > if ($DB =3D=3D "mysql") { > do something... > } > elseif ($DB =3D=3D "postgresql") { > do something else... > } > elseif ($DB =3D=3D "oracle") { > etc, etc > } >=20 > 2. Is still functionally the same as the current one (I don't think=20 > anyone wants to get into a database redesign). Let me clarify=20 > that...it's not just functionally the same, it is the same except we may= =20 > change some data types to something more generic and rename some fields=20 > to avoid keyword collisions. >=20 > So it would be the same generic schema for each database, but different=20 > creation scripts and things like that. At least, that's how I envision = it. Please, please avoid huge if/else blocks if possible. (Even if I did=20 not in the past.) I think that PEAR::DB will help avoid this in most=20 cases. By making phpESP database engine independant, use of neat DB=20 =66eatures will likely have to be sacrificed. When it comes down to it,=20 if a suitible ``enum'' type does not exist accross the board (in a way=20 that will be acessible with the same SQL query), then just use a numeric=20 type, and map it to an enumeration only inside the PHP code. If NULL is=20 not available as a default, don't use it, use -1 and remap all internal=20 representation that needs it. I really hope that NULL will be an=20 option, because it is the best way to represent the lack of a value.=20 NULL is especially important in the response data to indicate that the=20 question was left blank. Perhaps, we will have to avoid counting on=20 defaults all together, and explicitly set all fields from the code. If all else fails, and there is someplace where it looks like an if/else=20 is needed, then try to avoid it with OO/polymorphism. This may be a=20 better general approach anyway, with objects representing the database=20 tables. I have consitently found that some of the phpesp data is poorly suited=20 =66or storage in a relational db. This is compounded by the fact that=20 mysql (which was the initial customer reqirement) was much happier with=20 a few tables with lots of records than lots of tables with few records.=20 I believe XML w/ a well desinged schema/dtd (using some unknown sort=20 of storage) would be far better for the representation of the survey=20 data (and could provide multi-lingual support much more redily than the=20 current organization). User/group tables are probably best done with=20 some traditional db or directory (SQL or LDAP). -James ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only for= = the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only for= = the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=3Dmm/g22lp.tmpl= =20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only for= = the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D |
From: Charlie S. <Sm...@ld...> - 2003-11-18 17:09:09
|
On 11/18/03 10:00AM Charlie Smith wrote: <snip> Let's make all mysql declarations of 'NOT NULL default ', become NULL by = definition. </snip> Sorry guys, I meant to write .... NOT NULL default '' so this would = only apply to those columns that would default to the empty string in the = mysql definition. ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only for= = the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D |
From: Charlie S. <Sm...@ld...> - 2003-11-18 17:04:16
|
Oops, forgot to include the attached Oracle library. >>> Charlie Smith 11/18/03 10:00AM >>> Let's make all mysql declarations of 'NOT NULL default ', become NULL by = definition. It appears that Oracle will have to be dealt with in the at = the code level when dealing with the mysql empty string. We may be able = to abstract this to by passing the query statement through some type of = parser, but I'm not sure how clean this would be. So far, it looks like we've got Stephan, Sean and Jeremy Buchman who have = volunteered on this project. I'll try and get the schema for Oracle in = my next email to you all. This should firm up the datbase design for the = Oracle schema. =20 I'm thinking that by using the PEAR DB library, those wanting to stay with = mysql could just substitute the PEAR DB calls in your unit testing, as you = go. So, whether using PEAR DB in some calls and direct mysql calls in = others, it should work. I've attached oracleIncBeta.php, the Oracle versions for all the mysql = calls I have identified as being used in the phpESP. Most were pretty = straigt-forward to handle. There was one that I'd like to see if we can = dispose of, however. See if you can guess which one it is. =20 Please take a look at these routines (there mysql counterpart would be = mysql_connect for oracleConnect, mysql_close for oracleClose, etc.) and = assist in identfying the PEAR DB function that would take it's place. I'd like to propose we use ORACLE as the test platform. Or at least, I'd = like to see the end product work with Oracle as one of the standard databases. I'll attach the Oracle schema in my next = posting. There are 13 functions. If you would like to sign up for one, please mark = your name or initials next to the routine. Please list the name of the identical PEAR DB fuction, if there is on. If = not please indicate. Mark TESTED with an 'x/ORACLE' to show test complete on Oracle platform. Mark INIT with your initials and then add a date when test complete. ex. = cws. ex. cws-11/18/03=20 function PEAR DB = TESTED/Platform INIT/Date =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D= =3D oracleConnect oracleClose oracleQuery oracleFetchArray oracleNumRows oracleExecuteQuery oracleFetchRow oracleError() oracleFreeResult oracleInsertId oracleResult oracleSelectDB oracleAffectedRows Charlie 11/18/03 Charlie Smith wrote on 10/24/03 10:26AM: <snip> Calling for help - W O U L D A N Y O N E B E INTERESTED = IN ASSISTING WITH THE PORT OF MYSQL TO PEAR DB? If so, please respond, and I'll try and divy = out assignments. </snip> >>> "Charlie Smith" <Sm...@ld...> 10/06/03 07:28AM >>> So code would be modified to be: if (mystring=3D=3D'') mysql=3D'select * from designer where username is null'; else mysql=3D'select * from designer where username =3D ' + quotefunc(mystring= ); See http://www.tek-tips.com/viewthread.cfm?spid=3D759&newpid=3D759&sqid=3D6= 57480 for further discussion on topic of empty string. >>> "Charlie Smith" <Sm...@ld...> 10/02/03 01:51PM >>> Yes, the use of PEARDB should make the long if's largely unnecessary. For field definitions, I'd be inclined to go with NULLs as well. We'd use = the NULL and NOT NULL qualifier in the field definitions and work out the = default values in the code. So we'd keep fields defined as NOT NULL in = Oracle. The field definition of fieldname ... NOT NULL default '' is = not valid in Oracle. Also, in Oracle, NULL fields are detected differentl= y that fields with data in them when using a select statement. ie. select = * from table where field IS null=20 would be the code for going against the Oracle table rather than select = * from table where field =3D null (This is an invalid select as you = have to use 'is' and 'is not' null when detecting null fields in the = oracle tables, not =3D and !=3D. So if there is code in phpESP which = references empty string in select statements, it would need to be = modified. I had thought we may want to replace the NOT NULL default '' with just = default ' '. But had my reservations. Thanks for your input on this, = though I confess I am still a bit confused. In Oracle if there is no = supplied value for a nullable field (any field not declared as NOT NULL), = it's value is NULL by default. If you had a choice between default NULL = and NOT NULL, which would you want to go with? =20 For following fields we could translate to Oracle as follows? MySQL becomes Oracle int(10) unsigned NOT NULL default '0' NOT NULL default NULL, NULL int(10) unsigned default '0' default 0 enum('Y','N') NOT NULL default 'N' NOT NULL (with check constraint= *) NOT NULL default '' NOT NULL * check constraint syntax: alter table designer add constraint designer_pdesign_ck check (pdesign in ('Y','N')); We could also put a trigger on the table/field so that on insert or = update, if the new field value were null, it would get populated with = 'N'. We could handle all the other default values this way except for the = empty string ''. We'd have to modify the code for this where it = selects from table where field =3D ''. For ENUM types, a check constraint can be used in Oracle, to make sure = values are matched against those we want to allow. What would the syntax look like in PostGres? Does this sound agreeable? >>> "James E. Flemer" <jf...@uv...> 10/01/03 06:43PM >>> Jeremy Buchmann wrote: > On Wednesday, October 1, 2003, at 02:13 PM, Stefan Champailler wrote: >=20 >>> With that: >>> Let's discuss how to handle the schemas >>> 1) ENUM type in PostGreSQL and Oracle. >>> 2) the empty string in default values >>> 3) default values vs NOT NULL >> >> >> My Oracle and PostgreSQL is limited, so I ask the question : are we=20 >> planning >> to make severeal schema with the hope to have minimum code rewrite on = the >> phpESP side ? (I guess it makes sense). >> >=20 > I think it's best to work out a schema that: >=20 > 1. Is as generic as possible so we can avoid or minimize code like = this: >=20 > if ($DB =3D=3D "mysql") { > do something... > } > elseif ($DB =3D=3D "postgresql") { > do something else... > } > elseif ($DB =3D=3D "oracle") { > etc, etc > } >=20 > 2. Is still functionally the same as the current one (I don't think=20 > anyone wants to get into a database redesign). Let me clarify=20 > that...it's not just functionally the same, it is the same except we = may=20 > change some data types to something more generic and rename some = fields=20 > to avoid keyword collisions. >=20 > So it would be the same generic schema for each database, but = different=20 > creation scripts and things like that. At least, that's how I envision = it. Please, please avoid huge if/else blocks if possible. (Even if I did=20 not in the past.) I think that PEAR::DB will help avoid this in most=20 cases. By making phpESP database engine independant, use of neat DB=20 features will likely have to be sacrificed. When it comes down to it,=20 if a suitible ``enum'' type does not exist accross the board (in a way=20 that will be acessible with the same SQL query), then just use a numeric=20= type, and map it to an enumeration only inside the PHP code. If NULL = is=20 not available as a default, don't use it, use -1 and remap all internal=20 representation that needs it. I really hope that NULL will be an=20 option, because it is the best way to represent the lack of a value.=20 NULL is especially important in the response data to indicate that the=20 question was left blank. Perhaps, we will have to avoid counting on=20 defaults all together, and explicitly set all fields from the code. If all else fails, and there is someplace where it looks like an if/else=20= is needed, then try to avoid it with OO/polymorphism. This may be a=20 better general approach anyway, with objects representing the database=20 tables. I have consitently found that some of the phpesp data is poorly suited=20 for storage in a relational db. This is compounded by the fact that=20 mysql (which was the initial customer reqirement) was much happier with=20 a few tables with lots of records than lots of tables with few records.=20 I believe XML w/ a well desinged schema/dtd (using some unknown sort=20 of storage) would be far better for the representation of the survey=20 data (and could provide multi-lingual support much more redily than the=20 current organization). User/group tables are probably best done with=20 some traditional db or directory (SQL or LDAP). -James ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only = for the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only = for the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 |
From: Charlie S. <Sm...@ld...> - 2003-11-18 17:01:16
|
Let's make all mysql declarations of 'NOT NULL default ', become NULL by = definition. It appears that Oracle will have to be dealt with in the at = the code level when dealing with the mysql empty string. We may be able = to abstract this to by passing the query statement through some type of = parser, but I'm not sure how clean this would be. So far, it looks like we've got Stephan, Sean and Jeremy Buchman who have = volunteered on this project. I'll try and get the schema for Oracle in = my next email to you all. This should firm up the datbase design for the = Oracle schema. =20 I'm thinking that by using the PEAR DB library, those wanting to stay with = mysql could just substitute the PEAR DB calls in your unit testing, as you = go. So, whether using PEAR DB in some calls and direct mysql calls in = others, it should work. I've attached oracleIncBeta.php, the Oracle versions for all the mysql = calls I have identified as being used in the phpESP. Most were pretty = straigt-forward to handle. There was one that I'd like to see if we can = dispose of, however. See if you can guess which one it is. =20 Please take a look at these routines (there mysql counterpart would be = mysql_connect for oracleConnect, mysql_close for oracleClose, etc.) and = assist in identfying the PEAR DB function that would take it's place. I'd like to propose we use ORACLE as the test platform. Or at least, I'd = like to see the end product work with Oracle as one of the standard databases. I'll attach the Oracle schema in my next = posting. There are 13 functions. If you would like to sign up for one, please mark = your name or initials next to the routine. Please list the name of the identical PEAR DB fuction, if there is on. If = not please indicate. Mark TESTED with an 'x/ORACLE' to show test complete on Oracle platform. Mark INIT with your initials and then add a date when test complete. ex. = cws. ex. cws-11/18/03=20 function PEAR DB = TESTED/Platform INIT/Date =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D= =3D oracleConnect oracleClose oracleQuery oracleFetchArray oracleNumRows oracleExecuteQuery oracleFetchRow oracleError() oracleFreeResult oracleInsertId oracleResult oracleSelectDB oracleAffectedRows Charlie 11/18/03 Charlie Smith wrote on 10/24/03 10:26AM: <snip> Calling for help - W O U L D A N Y O N E B E INTERESTED = IN ASSISTING WITH THE PORT OF MYSQL TO PEAR DB? If so, please respond, and I'll try and divy = out assignments. </snip> >>> "Charlie Smith" <Sm...@ld...> 10/06/03 07:28AM >>> So code would be modified to be: if (mystring=3D=3D'') mysql=3D'select * from designer where username is null'; else mysql=3D'select * from designer where username =3D ' + quotefunc(mystring= ); See http://www.tek-tips.com/viewthread.cfm?spid=3D759&newpid=3D759&sqid=3D6= 57480 for further discussion on topic of empty string. >>> "Charlie Smith" <Sm...@ld...> 10/02/03 01:51PM >>> Yes, the use of PEARDB should make the long if's largely unnecessary. For field definitions, I'd be inclined to go with NULLs as well. We'd use = the NULL and NOT NULL qualifier in the field definitions and work out the = default values in the code. So we'd keep fields defined as NOT NULL in = Oracle. The field definition of fieldname ... NOT NULL default '' is = not valid in Oracle. Also, in Oracle, NULL fields are detected differentl= y that fields with data in them when using a select statement. ie. select = * from table where field IS null=20 would be the code for going against the Oracle table rather than select = * from table where field =3D null (This is an invalid select as you = have to use 'is' and 'is not' null when detecting null fields in the = oracle tables, not =3D and !=3D. So if there is code in phpESP which = references empty string in select statements, it would need to be = modified. I had thought we may want to replace the NOT NULL default '' with just = default ' '. But had my reservations. Thanks for your input on this, = though I confess I am still a bit confused. In Oracle if there is no = supplied value for a nullable field (any field not declared as NOT NULL), = it's value is NULL by default. If you had a choice between default NULL = and NOT NULL, which would you want to go with? =20 For following fields we could translate to Oracle as follows? MySQL becomes Oracle int(10) unsigned NOT NULL default '0' NOT NULL default NULL, NULL int(10) unsigned default '0' default 0 enum('Y','N') NOT NULL default 'N' NOT NULL (with check constraint= *) NOT NULL default '' NOT NULL * check constraint syntax: alter table designer add constraint designer_pdesign_ck check (pdesign in ('Y','N')); We could also put a trigger on the table/field so that on insert or = update, if the new field value were null, it would get populated with = 'N'. We could handle all the other default values this way except for the = empty string ''. We'd have to modify the code for this where it = selects from table where field =3D ''. For ENUM types, a check constraint can be used in Oracle, to make sure = values are matched against those we want to allow. What would the syntax look like in PostGres? Does this sound agreeable? >>> "James E. Flemer" <jf...@uv...> 10/01/03 06:43PM >>> Jeremy Buchmann wrote: > On Wednesday, October 1, 2003, at 02:13 PM, Stefan Champailler wrote: >=20 >>> With that: >>> Let's discuss how to handle the schemas >>> 1) ENUM type in PostGreSQL and Oracle. >>> 2) the empty string in default values >>> 3) default values vs NOT NULL >> >> >> My Oracle and PostgreSQL is limited, so I ask the question : are we=20 >> planning >> to make severeal schema with the hope to have minimum code rewrite on = the >> phpESP side ? (I guess it makes sense). >> >=20 > I think it's best to work out a schema that: >=20 > 1. Is as generic as possible so we can avoid or minimize code like = this: >=20 > if ($DB =3D=3D "mysql") { > do something... > } > elseif ($DB =3D=3D "postgresql") { > do something else... > } > elseif ($DB =3D=3D "oracle") { > etc, etc > } >=20 > 2. Is still functionally the same as the current one (I don't think=20 > anyone wants to get into a database redesign). Let me clarify=20 > that...it's not just functionally the same, it is the same except we = may=20 > change some data types to something more generic and rename some = fields=20 > to avoid keyword collisions. >=20 > So it would be the same generic schema for each database, but = different=20 > creation scripts and things like that. At least, that's how I envision = it. Please, please avoid huge if/else blocks if possible. (Even if I did=20 not in the past.) I think that PEAR::DB will help avoid this in most=20 cases. By making phpESP database engine independant, use of neat DB=20 features will likely have to be sacrificed. When it comes down to it,=20 if a suitible ``enum'' type does not exist accross the board (in a way=20 that will be acessible with the same SQL query), then just use a numeric=20= type, and map it to an enumeration only inside the PHP code. If NULL = is=20 not available as a default, don't use it, use -1 and remap all internal=20 representation that needs it. I really hope that NULL will be an=20 option, because it is the best way to represent the lack of a value.=20 NULL is especially important in the response data to indicate that the=20 question was left blank. Perhaps, we will have to avoid counting on=20 defaults all together, and explicitly set all fields from the code. If all else fails, and there is someplace where it looks like an if/else=20= is needed, then try to avoid it with OO/polymorphism. This may be a=20 better general approach anyway, with objects representing the database=20 tables. I have consitently found that some of the phpesp data is poorly suited=20 for storage in a relational db. This is compounded by the fact that=20 mysql (which was the initial customer reqirement) was much happier with=20 a few tables with lots of records than lots of tables with few records.=20 I believe XML w/ a well desinged schema/dtd (using some unknown sort=20 of storage) would be far better for the representation of the survey=20 data (and could provide multi-lingual support much more redily than the=20 current organization). User/group tables are probably best done with=20 some traditional db or directory (SQL or LDAP). -James ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only = for the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only = for the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 |
From: Stefan C. <sch...@ea...> - 2003-11-13 20:46:18
|
> Because of the way you've rewritten the logic processing in some of the > code (for ex. mysql_num_rows), we'll need to take a good look at the time > it would take to rewrite phpesp to use that logic vs time to use the > structures, triggers, and sequencers that I've developed. heeemmm her.. Yes maybe whyn not ? :) I'm done now, just expecting the move to Oracle to happen soon. Overall, moving to PostgreSQL wasn't that hard. Just very time consuming. It took me roughly 10 days, using triggers to emulate auto_increment and a bit of glue to avoid "last_insert_id". PostgreSQL also let me use foreign keys like hell, although it costs some performance, I think that data integrity is nice to have (mySQL documentation about foreing keys is kind of scary). On the PEAR side, since I saw that it doesn't help me a lot in the porting area, I think that using ODBC was a good idea : the parts explained above had to be done anyway, PEAR or not. > These structures > that I've incorporated into the ORACLE schema would probably be more easily > used to rewrite the phpESP mysql function calls. I say this only because > I'm more familiar with triggers, sequencers and things needed in Oracle. Those where helpful, this is the one I've used : CREATE SEQUENCE global_id; CREATE OR REPLACE FUNCTION get_unique_id() RETURNS TRIGGER AS ' BEGIN IF NEW.id IS NULL THEN NEW.id = nextval(''global_id''); END IF; RETURN NEW; END; ' LANGUAGE 'plpgsql'; stF > We'll need to compare notes on this as you've now more expertise in > PostgreSQL. BTW: is PostgreSQL formally supported with the PEAR DB stuff? > > I've only got a couple responses to "call for developers" on the PORT to > PEAR DB. Isn't there anyone else that would be interested? > > >>> "Stefan Champailler" <sch...@ea...> 11/06/03 03:57AM >>> > > Continuing port to PostgreSQL on IIS. I think that the ODBC layer has > troubles if one doesn't call "odbc_free_result" properly. Be aware of that > because not doing so (if that is the problme, I can hardly prove that) > tends to lead to very strange behaviour. > > I'm also almost done with rewriting the DB tables. I'll send them here when > they'll be up and running on Oracle. > > stF > > > Continuing my work to port phpESP to ODBC/Oracle, I stumbled against a > > few problem because phpESP was primarily developped for mySQL. When > > moving to Oracle beware that there's no auto_increment and thus we must > > use sequence. To be able to predevelop outside the heavily controlled > > Oracle environment, I figured out that it'd be better if I used > > PostGreSQL, because it provides sequences and, more importantly, good > > support for subqueries (an area where MySQL traps you way too much in its > > own DB paradigm (IMHO)). Therefore, I'mprobably going to try to port > > everything to PostgreSQL and when I'm done, I'll move everything to > > Oracle. Again, it may sound a little overkill, but the DBA are so > > reluctant/busy to leave me alone in a ORA sand-box that I have to go my > > own way. > > > > stF > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > _______________________________________________ > > phpESP-devel mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpesp-devel > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel > > > > --------------------------------------------------------------------------- >--- This message may contain confidential information, and is intended only > for the use of the individual(s) to whom it is addressed. > > > =========================================================================== >=== |
From: SourceForge.net <no...@so...> - 2003-11-11 15:10:44
|
Bugs item #840004, was opened at 2003-11-11 07:10 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=840004&group_id=8956 Category: User Group: v1.6.1 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Entering '0' in text box Initial Comment: If you enter a '0' in a text box, the program ignores it and prompts you to "Enter a value..." (only if field is required) . Workaround: Changing the field to Numeric allows 0 as an entry. Demo site replicated at: <?php $sid=12170; include("/home/groups/p/ph/phpesp/htdocs/demo//public/ handler.php");?> Once activated you can also access the survey directly from the following URL. http://phpesp.sourceforge.net/demo/public/survey.php? name=0Bug email addy (backwards) is ude.csum [AT] adin Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=840004&group_id=8956 |
From: flobee <fl...@gm...> - 2003-11-09 15:17:11
|
Long time ago! now the solution! the timeout came from a missing index of the "username" in response ! now: its running too fast :-) with this you can find users without a survey done (to clean users from the db, because my is huge!) ALTER TABLE `response` ADD INDEX ( `username` ) $sql = ("SELECT t1.*, COUNT(t2.username) AS cnt FROM respondent AS t1 LEFT JOIN response AS t2 ON t1.username = t2.username WHERE t1.realm = '$my_realm' AND (t2.username is NULL OR t1.username = t2.username) GROUP BY t1.username ORDER BY cnt ASC "); $match = mysql_query( $sql ) or die ("$sql<br>". mysql_error()); while (list(..,...,.... .... ,$counts) = mysql_fetch_row($match)) { // do something } flobee ----- Original Message ----- From: "Luis Fagundes" <lfa...@fu...> To: "flobee" <fl...@gm...> Sent: Saturday, August 09, 2003 11:49 PM Subject: Re: [phpesp-dev] little help -> off topic > Hi! > try this: > > SELECT t1.*, max(t2.submitted) as mysort FROM respondent as t1 LEFT JOIN > response as t2 ON t1.username = t2.username WHERE t1.realm='$realm' > GROUP BY t1.username > > with LEFT JOIN if a row is not found in t2, null is returned. > > []s > Luis > > flobee wrote: > > >hello all! > >i´m working on a little tool to get some extra statistic informations about > >the respondents and the usage... > >i build a page with shows me the TOP lists of surverys, and respondents > > > >now i want the find out which respondent has not made or finished a survey > >to see it or to delete unused accounts (huge list!) but i really have > >troubles to find a right and simple mysql query to check this. i already ask > >in some mysql-communitys but havn´t got any resonse yet :-( > > > >the query to show all respondents with the last survey (but missing users > >with "no survey"): > > > > $sql = ("SELECT t1.* , max(t2.submitted) as mysort > > FROM respondent AS t1 , response AS t2 > > WHERE t1.realm='$realm' AND t1.username = > >t2.username > > GROUP BY t1.username > > ORDER BY mysort DSEC > > LIMIT 0, 50 > > "); > > > >i dont´find an working query to include all respondents even thouse who have > >not submitted any survey! > >mysql.com give an example but on my localhost i only get timeouts so that i > >can not find a good result/solution: > >mysql> SELECT table1.* FROM table1 > > -> LEFT JOIN table2 ON table1.id=table2.id > > -> WHERE table2.id IS NULL; > >This example finds all rows in table1 with an id value that is not present > >in table2 > > > >have you any idea to have a query which handle this!? > > > >kind regards > >flobee > > > > > > > > > >------------------------------------------------------- > >This SF.Net email sponsored by: Free pre-built ASP.NET sites including > >Data Reports, E-commerce, Portals, and Forums are available now. > >Download today and enter to win an XBOX or Visual Studio .NET. > >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > >_______________________________________________ > >phpESP-devel mailing list > >php...@li... > >https://lists.sourceforge.net/lists/listinfo/phpesp-devel > > > > > > > > |
From: Charlie S. <Sm...@ld...> - 2003-11-07 17:40:06
|
Rather I should have said "BTW: is ODBC formally supported by the PEAR DB? >>> "Charlie Smith" <Sm...@ld...> 11/07/03 10:22AM >>> Because of the way you've rewritten the logic processing in some of the cod= e= (for ex. mysql_num_rows), we'll need to take a good look at the time it = would take to rewrite phpesp to use that logic vs time to use the = structures, triggers, and sequencers that I've developed. These structures= = that I've incorporated into the ORACLE schema would probably be more easily= = used to rewrite the phpESP mysql function calls. I say this only because = I'm more familiar with triggers, sequencers and things needed in Oracle. = We'll need to compare notes on this as you've now more expertise in = PostgreSQL. BTW: is PostgreSQL formally supported with the PEAR DB stuff? I've only got a couple responses to "call for developers" on the PORT to = PEAR DB. Isn't there anyone else that would be interested? >>> "Stefan Champailler" <sch...@ea...> 11/06/03 03:57AM >>> Continuing port to PostgreSQL on IIS. I think that the ODBC layer has = troubles=20 if one doesn't call "odbc_free_result" properly. Be aware of that because = not=20 doing so (if that is the problme, I can hardly prove that) tends to lead to= =20 very strange behaviour. I'm also almost done with rewriting the DB tables. I'll send them here when= =20 they'll be up and running on Oracle. stF > Continuing my work to port phpESP to ODBC/Oracle, I stumbled against a few > problem because phpESP was primarily developped for mySQL. When moving to > Oracle beware that there's no auto_increment and thus we must use = sequence. > To be able to predevelop outside the heavily controlled Oracle = environment, > I figured out that it'd be better if I used PostGreSQL, because it = provides > sequences and, more importantly, good support for subqueries (an area = where > MySQL traps you way too much in its own DB paradigm (IMHO)). Therefore, > I'mprobably going to try to port everything to PostgreSQL and when I'm > done, I'll move everything to Oracle. Again, it may sound a little > overkill, but the DBA are so reluctant/busy to leave me alone in a ORA > sand-box that I have to go my own way. > > stF > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/=20 > _______________________________________________ > phpESP-devel mailing list > php...@li...=20 > https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only for= = the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only for= = the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D |
From: Charlie S. <Sm...@ld...> - 2003-11-07 17:23:23
|
Because of the way you've rewritten the logic processing in some of the cod= e= (for ex. mysql_num_rows), we'll need to take a good look at the time it = would take to rewrite phpesp to use that logic vs time to use the = structures, triggers, and sequencers that I've developed. These structures= = that I've incorporated into the ORACLE schema would probably be more easily= = used to rewrite the phpESP mysql function calls. I say this only because = I'm more familiar with triggers, sequencers and things needed in Oracle. = We'll need to compare notes on this as you've now more expertise in = PostgreSQL. BTW: is PostgreSQL formally supported with the PEAR DB stuff? I've only got a couple responses to "call for developers" on the PORT to = PEAR DB. Isn't there anyone else that would be interested? >>> "Stefan Champailler" <sch...@ea...> 11/06/03 03:57AM >>> Continuing port to PostgreSQL on IIS. I think that the ODBC layer has = troubles=20 if one doesn't call "odbc_free_result" properly. Be aware of that because = not=20 doing so (if that is the problme, I can hardly prove that) tends to lead to= =20 very strange behaviour. I'm also almost done with rewriting the DB tables. I'll send them here when= =20 they'll be up and running on Oracle. stF > Continuing my work to port phpESP to ODBC/Oracle, I stumbled against a few > problem because phpESP was primarily developped for mySQL. When moving to > Oracle beware that there's no auto_increment and thus we must use = sequence. > To be able to predevelop outside the heavily controlled Oracle = environment, > I figured out that it'd be better if I used PostGreSQL, because it = provides > sequences and, more importantly, good support for subqueries (an area = where > MySQL traps you way too much in its own DB paradigm (IMHO)). Therefore, > I'mprobably going to try to port everything to PostgreSQL and when I'm > done, I'll move everything to Oracle. Again, it may sound a little > overkill, but the DBA are so reluctant/busy to leave me alone in a ORA > sand-box that I have to go my own way. > > stF > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/=20 > _______________________________________________ > phpESP-devel mailing list > php...@li...=20 > https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/=20 _______________________________________________ phpESP-devel mailing list php...@li...=20 https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20 ---------------------------------------------------------------------------= --- This message may contain confidential information, and is intended only for= = the use of the individual(s) to whom it is addressed. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D |
From: Kon <ang...@ip...> - 2003-11-07 10:47:17
|
Hey Roman, I'll have a look at this over the weekend as I'm already doing some redesign work on my devel version. I'll let you know what I find. Regards Kon On Thu, 2003-11-06 at 21:06, Roman Yashin wrote: > I think I found it! (Haven't fixed it yet tho'). It's in > espresponse.inc, response_select_name() function. > > > > The problem is in returning $nam array (see line ~651). It's being > created couple of lines before with $nam[$key] = $val. > > > > I've done the following tests: > > > > First: count ($nam,COUNT_RECURSIVE) for > > $nam[$key] = $val // where $key = question name/label > > > > Second: count ($nam,COUNT_RECURSIVE) for > > $nam[] = $val // notice no variable for index > > > > The two arrays have different size, which I believe is incorrect. BTW, > the second array has correct data for CSV export. Something happens > when we use question names for indexes in the array. > > > > I hope all these make sense. I am afraid this behavior might surface > somewhere else. > > James, Kon and others I don't know: > > What do you guys think about it? > > > > > > Cheers, > > > > Roman > > > > > > > > -----Original Message----- > From: Roman Yashin [mailto:ro...@ss...] > Sent: Monday, November 03, 2003 7:06 PM > To: Matthew Gregg > Cc: php...@li... > Subject: Re: [phpesp-dev] CVS export possible bug > > > > Matthew, > > > > I know of Rank type behavior, I'm not talking about that. > > In my case, I am suing Radio Buttons and only two out of 50+ > questions > > getting messed up! > > > > Thanks for your help tho' > > > > Roman > > > > On Monday, November 3, 2003, at 06:10 PM, Matthew Gregg wrote: > > > > > Your problem might be related to this bug: > > > http://sourceforge.net/tracker/ > > > index.php?func=detail&aid=827824&group_id=8956&atid=108956 > > > > > > Try taking that "off by one" bug into account and see if the > > > frequencies > > > work out. > > > > > > On Mon, 2003-11-03 at 10:08, Roman Yashin wrote: > > >> Hi, > > >> > > >> > > >> > > >> I think there is a possible bug in CSV export function. There is > > >> always a chance that my dataset is messed up, but I don't think so. > > >> I'm doing more tests to eliminate that possibility. Meanwhile, has > > >> anyone experience the following: > > >> > > >> > > >> > > >> The frequencies for question choices on the report page DO NOT > > >> correspond to the frequencies for the same question when you > analyze > > >> it in SPSS or Excel? > > >> > > >> > > >> > > >> Example: > > >> > > >> Question: I believe there could a bug in CSV Export function. > > >> > > >> > > >> > > >> In ESP Report you get: > > >> > > >> Strongly Agree 8.8% (13) > > >> > > >> Agree 59.9% (88) > > >> > > >> Disagree 29.9% (44) > > >> > > >> Strongly Disagree 1.4% (2) > > >> > > >> TOTAL 100.0% 147 > > >> > > >> > > >> > > >> In CSV file you get (SPSS and Excel): > > >> > > >> Strongly Agree (16) > > >> > > >> Agree (78) > > >> > > >> Disagree (52) > > >> > > >> Strongly Disagree (1) > > >> > > >> TOTAL 100.0% 147 > > >> > > >> > > >> > > >> I should've probably made sure it is a bug before bothering you > all, > > >> but I figured if somebody has experienced something similar it will > > >> save me a great deal of time. > > >> > > >> > > >> > > >> Cheers, > > >> > > >> > > >> > > >> Roman > > >> > > >> > > > -- > > > mcg > > > ------------------------------------- > > > The IT Lab (http://www.itlab.musc.edu) > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > _______________________________________________ > > phpESP-devel mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpesp-devel > > |
From: Stefan C. <sch...@ea...> - 2003-11-06 20:39:38
|
Continuing port to PostgreSQL on IIS. I think that the ODBC layer has troubles if one doesn't call "odbc_free_result" properly. Be aware of that because not doing so (if that is the problme, I can hardly prove that) tends to lead to very strange behaviour. I'm also almost done with rewriting the DB tables. I'll send them here when they'll be up and running on Oracle. stF > Continuing my work to port phpESP to ODBC/Oracle, I stumbled against a few > problem because phpESP was primarily developped for mySQL. When moving to > Oracle beware that there's no auto_increment and thus we must use sequence. > To be able to predevelop outside the heavily controlled Oracle environment, > I figured out that it'd be better if I used PostGreSQL, because it provides > sequences and, more importantly, good support for subqueries (an area where > MySQL traps you way too much in its own DB paradigm (IMHO)). Therefore, > I'mprobably going to try to port everything to PostgreSQL and when I'm > done, I'll move everything to Oracle. Again, it may sound a little > overkill, but the DBA are so reluctant/busy to leave me alone in a ORA > sand-box that I have to go my own way. > > stF > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel |
From: Matthew G. <gr...@mu...> - 2003-11-06 15:18:20
|
If this turns out to be the cause, it is already fixed in CVS. See bug #789042 <http://sourceforge.net/tracker/?group_id=8956&atid=108956&func=detail&aid=789042> On Thu, 2003-11-06 at 09:55, Roman Yashin wrote: > Update: > > > > Had a chance to talk to Matthew (thanks to IRC) and he had a very > simple and brilliant idea! I think we've figured out what is > happening. > > When I designed this questionnaire, I let phpESP fill in the question > names for me. The problem is that I had some question that were worded > similarly, i.e. had different endings with the same beginnings. Don't > ask me why, I didn't come up with this questionnaire, but I can image > some standardized surveys being like that. This became a problem when > the names got trimmed to 30 characters and I tried to export data to > CSV. Anyhow, I think this is what happed. I haven't had a chance to > look at the part of the code that does the naming trick. I thought I > would keep you up-to-date, so you won't be looking in a wrong place. > > > > All the best, > > > > Roman > > > > -----Original Message----- > From: Roman Yashin [mailto:Ro...@ss...] > Sent: Thursday, November 06, 2003 12:06 PM > To: php...@li... > Subject: RE: [phpesp-dev] CVS export possible bug > > > > I think I found it! (Haven't fixed it yet tho'). It's in > espresponse.inc, response_select_name() function. > > > > The problem is in returning $nam array (see line ~651). It's being > created couple of lines before with $nam[$key] = $val. > > > > I've done the following tests: > > > > First: count ($nam,COUNT_RECURSIVE) for > > $nam[$key] = $val // where $key = question name/label > > > > Second: count ($nam,COUNT_RECURSIVE) for > > $nam[] = $val // notice no variable for index > > > > The two arrays have different size, which I believe is incorrect. BTW, > the second array has correct data for CSV export. Something happens > when we use question names for indexes in the array. > > > > I hope all these make sense. I am afraid this behavior might surface > somewhere else. > > James, Kon and others I don't know: > > What do you guys think about it? > > > > > > Cheers, > > > > Roman > > > > > > > > -----Original Message----- > From: Roman Yashin [mailto:ro...@ss...] > Sent: Monday, November 03, 2003 7:06 PM > To: Matthew Gregg > Cc: php...@li... > Subject: Re: [phpesp-dev] CVS export possible bug > > > > Matthew, > > > > I know of Rank type behavior, I'm not talking about that. > > In my case, I am suing Radio Buttons and only two out of 50+ > questions > > getting messed up! > > > > Thanks for your help tho' > > > > Roman > > > > On Monday, November 3, 2003, at 06:10 PM, Matthew Gregg wrote: > > > > > Your problem might be related to this bug: > > > http://sourceforge.net/tracker/ > > > index.php?func=detail&aid=827824&group_id=8956&atid=108956 > > > > > > Try taking that "off by one" bug into account and see if the > > > frequencies > > > work out. > > > > > > On Mon, 2003-11-03 at 10:08, Roman Yashin wrote: > > >> Hi, > > >> > > >> > > >> > > >> I think there is a possible bug in CSV export function. There is > > >> always a chance that my dataset is messed up, but I don't think so. > > >> I'm doing more tests to eliminate that possibility. Meanwhile, has > > >> anyone experience the following: > > >> > > >> > > >> > > >> The frequencies for question choices on the report page DO NOT > > >> correspond to the frequencies for the same question when you > analyze > > >> it in SPSS or Excel? > > >> > > >> > > >> > > >> Example: > > >> > > >> Question: I believe there could a bug in CSV Export function. > > >> > > >> > > >> > > >> In ESP Report you get: > > >> > > >> Strongly Agree 8.8% (13) > > >> > > >> Agree 59.9% (88) > > >> > > >> Disagree 29.9% (44) > > >> > > >> Strongly Disagree 1.4% (2) > > >> > > >> TOTAL 100.0% 147 > > >> > > >> > > >> > > >> In CSV file you get (SPSS and Excel): > > >> > > >> Strongly Agree (16) > > >> > > >> Agree (78) > > >> > > >> Disagree (52) > > >> > > >> Strongly Disagree (1) > > >> > > >> TOTAL 100.0% 147 > > >> > > >> > > >> > > >> I should've probably made sure it is a bug before bothering you > all, > > >> but I figured if somebody has experienced something similar it will > > >> save me a great deal of time. > > >> > > >> > > >> > > >> Cheers, > > >> > > >> > > >> > > >> Roman > > >> > > >> > > > -- > > > mcg > > > ------------------------------------- > > > The IT Lab (http://www.itlab.musc.edu) > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > _______________________________________________ > > phpESP-devel mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpesp-devel -- mcg ------------------------------------- The IT Lab (http://www.itlab.musc.edu) |
From: Roman Y. <Ro...@ss...> - 2003-11-06 14:56:10
|
Update: Had a chance to talk to Matthew (thanks to IRC) and he had a very simple and brilliant idea! I think we've figured out what is happening. When I designed this questionnaire, I let phpESP fill in the question names for me. The problem is that I had some question that were worded similarly, i.e. had different endings with the same beginnings. Don't ask me why, I didn't come up with this questionnaire, but I can image some standardized surveys being like that. This became a problem when the names got trimmed to 30 characters and I tried to export data to CSV. Anyhow, I think this is what happed. I haven't had a chance to look at the part of the code that does the naming trick. I thought I would keep you up-to-date, so you won't be looking in a wrong place. All the best, Roman -----Original Message----- From: Roman Yashin [mailto:Ro...@ss...] Sent: Thursday, November 06, 2003 12:06 PM To: php...@li... Subject: RE: [phpesp-dev] CVS export possible bug I think I found it! (Haven't fixed it yet tho'). It's in espresponse.inc, response_select_name() function. The problem is in returning $nam array (see line ~651). It's being created couple of lines before with $nam[$key] = $val. I've done the following tests: First: count ($nam,COUNT_RECURSIVE) for $nam[$key] = $val // where $key = question name/label Second: count ($nam,COUNT_RECURSIVE) for $nam[] = $val // notice no variable for index The two arrays have different size, which I believe is incorrect. BTW, the second array has correct data for CSV export. Something happens when we use question names for indexes in the array. I hope all these make sense. I am afraid this behavior might surface somewhere else. James, Kon and others I don't know: What do you guys think about it? Cheers, Roman -----Original Message----- From: Roman Yashin [mailto:ro...@ss...] Sent: Monday, November 03, 2003 7:06 PM To: Matthew Gregg Cc: php...@li... Subject: Re: [phpesp-dev] CVS export possible bug Matthew, I know of Rank type behavior, I'm not talking about that. In my case, I am suing Radio Buttons and only two out of 50+ questions getting messed up! Thanks for your help tho' Roman On Monday, November 3, 2003, at 06:10 PM, Matthew Gregg wrote: > Your problem might be related to this bug: > http://sourceforge.net/tracker/ > index.php?func=detail&aid=827824&group_id=8956&atid=108956 > > Try taking that "off by one" bug into account and see if the > frequencies > work out. > > On Mon, 2003-11-03 at 10:08, Roman Yashin wrote: >> Hi, >> >> >> >> I think there is a possible bug in CSV export function. There is >> always a chance that my dataset is messed up, but I don't think so. >> I'm doing more tests to eliminate that possibility. Meanwhile, has >> anyone experience the following: >> >> >> >> The frequencies for question choices on the report page DO NOT >> correspond to the frequencies for the same question when you analyze >> it in SPSS or Excel? >> >> >> >> Example: >> >> Question: I believe there could a bug in CSV Export function. >> >> >> >> In ESP Report you get: >> >> Strongly Agree 8.8% (13) >> >> Agree 59.9% (88) >> >> Disagree 29.9% (44) >> >> Strongly Disagree 1.4% (2) >> >> TOTAL 100.0% 147 >> >> >> >> In CSV file you get (SPSS and Excel): >> >> Strongly Agree (16) >> >> Agree (78) >> >> Disagree (52) >> >> Strongly Disagree (1) >> >> TOTAL 100.0% 147 >> >> >> >> I should've probably made sure it is a bug before bothering you all, >> but I figured if somebody has experienced something similar it will >> save me a great deal of time. >> >> >> >> Cheers, >> >> >> >> Roman >> >> > -- > mcg > ------------------------------------- > The IT Lab (http://www.itlab.musc.edu) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ phpESP-devel mailing list php...@li... https://lists.sourceforge.net/lists/listinfo/phpesp-devel |
From: Roman Y. <Ro...@ss...> - 2003-11-06 10:38:22
|
I've done some work on this issue before. This is how I did it: 1. Added [value] filed on the question design page for each question_choice. 2. Stored it in the question_choice value field. Stared adding some reporting functionality, but had to switch my focus to something else. Haven't implemented anything for CSV export, but can probably get to it now. Please let me know if you think it is the way to do it (set 1 and 2). All the best, Roman -----Original Message----- From: Roman Yashin [mailto:Ro...@ss...] Sent: Thursday, November 06, 2003 12:06 PM To: php...@li... Subject: RE: [phpesp-dev] CVS export possible bug I think I found it! (Haven't fixed it yet tho'). It's in espresponse.inc, response_select_name() function. The problem is in returning $nam array (see line ~651). It's being created couple of lines before with $nam[$key] = $val. I've done the following tests: First: count ($nam,COUNT_RECURSIVE) for $nam[$key] = $val // where $key = question name/label Second: count ($nam,COUNT_RECURSIVE) for $nam[] = $val // notice no variable for index The two arrays have different size, which I believe is incorrect. BTW, the second array has correct data for CSV export. Something happens when we use question names for indexes in the array. I hope all these make sense. I am afraid this behavior might surface somewhere else. James, Kon and others I don't know: What do you guys think about it? Cheers, Roman -----Original Message----- From: Roman Yashin [mailto:ro...@ss...] Sent: Monday, November 03, 2003 7:06 PM To: Matthew Gregg Cc: php...@li... Subject: Re: [phpesp-dev] CVS export possible bug Matthew, I know of Rank type behavior, I'm not talking about that. In my case, I am suing Radio Buttons and only two out of 50+ questions getting messed up! Thanks for your help tho' Roman On Monday, November 3, 2003, at 06:10 PM, Matthew Gregg wrote: > Your problem might be related to this bug: > http://sourceforge.net/tracker/ > index.php?func=detail&aid=827824&group_id=8956&atid=108956 > > Try taking that "off by one" bug into account and see if the > frequencies > work out. > > On Mon, 2003-11-03 at 10:08, Roman Yashin wrote: >> Hi, >> >> >> >> I think there is a possible bug in CSV export function. There is >> always a chance that my dataset is messed up, but I don't think so. >> I'm doing more tests to eliminate that possibility. Meanwhile, has >> anyone experience the following: >> >> >> >> The frequencies for question choices on the report page DO NOT >> correspond to the frequencies for the same question when you analyze >> it in SPSS or Excel? >> >> >> >> Example: >> >> Question: I believe there could a bug in CSV Export function. >> >> >> >> In ESP Report you get: >> >> Strongly Agree 8.8% (13) >> >> Agree 59.9% (88) >> >> Disagree 29.9% (44) >> >> Strongly Disagree 1.4% (2) >> >> TOTAL 100.0% 147 >> >> >> >> In CSV file you get (SPSS and Excel): >> >> Strongly Agree (16) >> >> Agree (78) >> >> Disagree (52) >> >> Strongly Disagree (1) >> >> TOTAL 100.0% 147 >> >> >> >> I should've probably made sure it is a bug before bothering you all, >> but I figured if somebody has experienced something similar it will >> save me a great deal of time. >> >> >> >> Cheers, >> >> >> >> Roman >> >> > -- > mcg > ------------------------------------- > The IT Lab (http://www.itlab.musc.edu) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ phpESP-devel mailing list php...@li... https://lists.sourceforge.net/lists/listinfo/phpesp-devel |
From: Roman Y. <Ro...@ss...> - 2003-11-06 10:07:00
|
I think I found it! (Haven't fixed it yet tho'). It's in espresponse.inc, response_select_name() function. The problem is in returning $nam array (see line ~651). It's being created couple of lines before with $nam[$key] = $val. I've done the following tests: First: count ($nam,COUNT_RECURSIVE) for $nam[$key] = $val // where $key = question name/label Second: count ($nam,COUNT_RECURSIVE) for $nam[] = $val // notice no variable for index The two arrays have different size, which I believe is incorrect. BTW, the second array has correct data for CSV export. Something happens when we use question names for indexes in the array. I hope all these make sense. I am afraid this behavior might surface somewhere else. James, Kon and others I don't know: What do you guys think about it? Cheers, Roman -----Original Message----- From: Roman Yashin [mailto:ro...@ss...] Sent: Monday, November 03, 2003 7:06 PM To: Matthew Gregg Cc: php...@li... Subject: Re: [phpesp-dev] CVS export possible bug Matthew, I know of Rank type behavior, I'm not talking about that. In my case, I am suing Radio Buttons and only two out of 50+ questions getting messed up! Thanks for your help tho' Roman On Monday, November 3, 2003, at 06:10 PM, Matthew Gregg wrote: > Your problem might be related to this bug: > http://sourceforge.net/tracker/ > index.php?func=detail&aid=827824&group_id=8956&atid=108956 > > Try taking that "off by one" bug into account and see if the > frequencies > work out. > > On Mon, 2003-11-03 at 10:08, Roman Yashin wrote: >> Hi, >> >> >> >> I think there is a possible bug in CSV export function. There is >> always a chance that my dataset is messed up, but I don't think so. >> I'm doing more tests to eliminate that possibility. Meanwhile, has >> anyone experience the following: >> >> >> >> The frequencies for question choices on the report page DO NOT >> correspond to the frequencies for the same question when you analyze >> it in SPSS or Excel? >> >> >> >> Example: >> >> Question: I believe there could a bug in CSV Export function. >> >> >> >> In ESP Report you get: >> >> Strongly Agree 8.8% (13) >> >> Agree 59.9% (88) >> >> Disagree 29.9% (44) >> >> Strongly Disagree 1.4% (2) >> >> TOTAL 100.0% 147 >> >> >> >> In CSV file you get (SPSS and Excel): >> >> Strongly Agree (16) >> >> Agree (78) >> >> Disagree (52) >> >> Strongly Disagree (1) >> >> TOTAL 100.0% 147 >> >> >> >> I should've probably made sure it is a bug before bothering you all, >> but I figured if somebody has experienced something similar it will >> save me a great deal of time. >> >> >> >> Cheers, >> >> >> >> Roman >> >> > -- > mcg > ------------------------------------- > The IT Lab (http://www.itlab.musc.edu) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ phpESP-devel mailing list php...@li... https://lists.sourceforge.net/lists/listinfo/phpesp-devel |
From: SourceForge.net <no...@so...> - 2003-11-05 19:55:59
|
Feature Requests item #836743, was opened at 2003-11-05 13:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=836743&group_id=8956 Category: None Group: None Status: Open Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: csv export field code instead of text Initial Comment: Hello. It would be nice if there were a way of specifying how the CSV file would represent the survey responses. I am looking at a survey that has about 100 radio button answers. When I get the mail confirmation of the response it look like this: 3474 : 6630 (Annotations keep important information with... 3475 : 6631 (Copy/paste URLs from browser to word... 3476 : 6635 (Author, copyright, title, URL, comments) 3477 : 6643 (e. All of the above) What would be ideal would be if the CSV output would have the field codes as the column names (3474...) and the field values stored as a number. The problem that I have right now is that I have to manually go through the responses and perform replace commands manually so that I will have data that will play nicely with SPSS. (Actually, I am putting it into Access, but it will eventually find its way out.) Thanks for thinking about this, or letting me know if I am missing something obvious. Cheers, --chris ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=836743&group_id=8956 |
From: Roman Y. <Ro...@ss...> - 2003-11-04 06:23:29
|
I'm pretty sure now it's a bug. I just imported the same data using ODBC connection and now spreadsheet's numbers correspond to the results on the report page. Maybe it is something in response_select_name()? Any feedback is highly appreciated. Roman -----Original Message----- From: Roman Yashin [mailto:ro...@ss...] Sent: Monday, November 03, 2003 7:06 PM To: Matthew Gregg Cc: php...@li... Subject: Re: [phpesp-dev] CVS export possible bug Matthew, I know of Rank type behavior, I'm not talking about that. In my case, I am suing Radio Buttons and only two out of 50+ questions getting messed up! Thanks for your help tho' Roman On Monday, November 3, 2003, at 06:10 PM, Matthew Gregg wrote: > Your problem might be related to this bug: > http://sourceforge.net/tracker/ > index.php?func=detail&aid=827824&group_id=8956&atid=108956 > > Try taking that "off by one" bug into account and see if the > frequencies > work out. > > On Mon, 2003-11-03 at 10:08, Roman Yashin wrote: >> Hi, >> >> >> >> I think there is a possible bug in CSV export function. There is >> always a chance that my dataset is messed up, but I don't think so. >> I'm doing more tests to eliminate that possibility. Meanwhile, has >> anyone experience the following: >> >> >> >> The frequencies for question choices on the report page DO NOT >> correspond to the frequencies for the same question when you analyze >> it in SPSS or Excel? >> >> >> >> Example: >> >> Question: I believe there could a bug in CSV Export function. >> >> >> >> In ESP Report you get: >> >> Strongly Agree 8.8% (13) >> >> Agree 59.9% (88) >> >> Disagree 29.9% (44) >> >> Strongly Disagree 1.4% (2) >> >> TOTAL 100.0% 147 >> >> >> >> In CSV file you get (SPSS and Excel): >> >> Strongly Agree (16) >> >> Agree (78) >> >> Disagree (52) >> >> Strongly Disagree (1) >> >> TOTAL 100.0% 147 >> >> >> >> I should've probably made sure it is a bug before bothering you all, >> but I figured if somebody has experienced something similar it will >> save me a great deal of time. >> >> >> >> Cheers, >> >> >> >> Roman >> >> > -- > mcg > ------------------------------------- > The IT Lab (http://www.itlab.musc.edu) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ phpESP-devel mailing list php...@li... https://lists.sourceforge.net/lists/listinfo/phpesp-devel |
From: Roman Y. <ro...@ss...> - 2003-11-03 17:06:08
|
Matthew, I know of Rank type behavior, I'm not talking about that. In my case, I am suing Radio Buttons and only two out of 50+ questions getting messed up! Thanks for your help tho' Roman On Monday, November 3, 2003, at 06:10 PM, Matthew Gregg wrote: > Your problem might be related to this bug: > http://sourceforge.net/tracker/ > index.php?func=detail&aid=827824&group_id=8956&atid=108956 > > Try taking that "off by one" bug into account and see if the > frequencies > work out. > > On Mon, 2003-11-03 at 10:08, Roman Yashin wrote: >> Hi, >> >> >> >> I think there is a possible bug in CSV export function. There is >> always a chance that my dataset is messed up, but I don't think so. >> I'm doing more tests to eliminate that possibility. Meanwhile, has >> anyone experience the following: >> >> >> >> The frequencies for question choices on the report page DO NOT >> correspond to the frequencies for the same question when you analyze >> it in SPSS or Excel? >> >> >> >> Example: >> >> Question: I believe there could a bug in CSV Export function. >> >> >> >> In ESP Report you get: >> >> Strongly Agree 8.8% (13) >> >> Agree 59.9% (88) >> >> Disagree 29.9% (44) >> >> Strongly Disagree 1.4% (2) >> >> TOTAL 100.0% 147 >> >> >> >> In CSV file you get (SPSS and Excel): >> >> Strongly Agree (16) >> >> Agree (78) >> >> Disagree (52) >> >> Strongly Disagree (1) >> >> TOTAL 100.0% 147 >> >> >> >> I should've probably made sure it is a bug before bothering you all, >> but I figured if somebody has experienced something similar it will >> save me a great deal of time. >> >> >> >> Cheers, >> >> >> >> Roman >> >> > -- > mcg > ------------------------------------- > The IT Lab (http://www.itlab.musc.edu) |
From: Roman Y. <Ro...@ss...> - 2003-11-03 15:09:01
|
Hi, I think there is a possible bug in CSV export function. There is always a chance that my dataset is messed up, but I don't think so. I'm doing more tests to eliminate that possibility. Meanwhile, has anyone experience the following: The frequencies for question choices on the report page DO NOT correspond to the frequencies for the same question when you analyze it in SPSS or Excel? Example: Question: I believe there could a bug in CSV Export function. In ESP Report you get: Strongly Agree 8.8% (13) Agree 59.9% (88) Disagree 29.9% (44) Strongly Disagree 1.4% (2) TOTAL 100.0% 147 In CSV file you get (SPSS and Excel): Strongly Agree (16) Agree (78) Disagree (52) Strongly Disagree (1) TOTAL 100.0% 147 I should've probably made sure it is a bug before bothering you all, but I figured if somebody has experienced something similar it will save me a great deal of time. Cheers, Roman |
From: Stefan C. <sch...@ea...> - 2003-10-29 19:58:12
|
I ame done with that. Main difficulties where : - Paths not correct (double slashes, and why does one include a trailing slash to the path definition ??? (and sometimes not btw :))) - http authorisation broken (sems like some $_SERVER[] variable are not as easy to get as on Apache). I'll transmit you my fix as soon as I have transferred it on my Linux machine). For the rest, it just went like a breeze (ODBC is really easy on Windows). Biggest unsolved trouble : email sending. I still don't know how to do that. I've seen people using COM objects (CDONTS or something like that), but it doesn't work for me (I'm pretty far from being an expert, so I may miss some important stuff) stF |
From: Stefan C. <sch...@ea...> - 2003-10-29 19:51:31
|
Continuing my work to port phpESP to ODBC/Oracle, I stumbled against a few problem because phpESP was primarily developped for mySQL. When moving to Oracle beware that there's no auto_increment and thus we must use sequence. To be able to predevelop outside the heavily controlled Oracle environment, I figured out that it'd be better if I used PostGreSQL, because it provides sequences and, more importantly, good support for subqueries (an area where MySQL traps you way too much in its own DB paradigm (IMHO)). Therefore, I'mprobably going to try to port everything to PostgreSQL and when I'm done, I'll move everything to Oracle. Again, it may sound a little overkill, but the DBA are so reluctant/busy to leave me alone in a ORA sand-box that I have to go my own way. stF |
From: Stefan C. <sch...@ea...> - 2003-10-28 19:00:13
|
Hi all, I'va also started to port phpESP to IIS/PHP (my final target is 2000/IIS/PHP/ ODBC/Oracle). Right now, the only thing I've seen is the "\" vs "/" usual problems. stF |
From: Stefan C. <sch...@ea...> - 2003-10-28 07:47:34
|
> Thanks for your reply Stephan. =A0Please keep postings copied to the grou= p if > possible. > > I believe it in our best interest to work together as well. > > Calling for help - =A0 W =A0O =A0U =A0L =A0D =A0 =A0 A N Y O N E =A0 =A0B= E =A0 =A0 =A0 INTERESTED > IN ASSISTING WITH THE PORT OF MYSQL TO PEAR DB? =A0If so, please respond,= and > I'll try and divy out assignments. > > Stephan, =A0 is the odbc stuff able to be abstracted to PEAR DB? As I already went into the process or rewriting the code to avoid=20 "mysql_insert_id" and "get row by numbers", I think I can be helpful.=20 However, please keep in mind that I had to change several SQL statement for= =20 my own need. I'll try to post a list of patch against all the sql soon. It= =20 can just help to see what I went through. Please note that some of the=20 rewrites were big (understand : I've entirely re-written some files). stF |
From: Stefan C. <sch...@ea...> - 2003-10-28 07:37:13
|
Dear you all, I DON'T WANT to start any flame here but the code quality of phpEsp is rather poor. Lots of replicated code ("go to management" links, authentification, queries,...). I raise a hand here because one of my managers totally disagrees with the use of PHP stuff (because they have coldfusion licenses) and I fear he's gonna watch the code and say "Mr Champailler you 're just a very bad coder, code is way too hard to maintain". I just tell that to you so that you think about it before going that direction. I had an enormous advantage with phpEsp in hand : it's there, it works and it allowed me to work on the specification _before_ writing too much code, just because it was there as a very good basis for the job. Unfortunately, I just realize that this advantage it's pretty hard to explain (dollars?) to a manager (although a technical one). I'm stating the obvious, but now that I see how easy it is to forget it, I just feel the urge to talk about it :) So this was more to share an experience rather than to criticize things I didn't make myself. Don't go mad, I love you all :) stF |
From: Stefan C. <sch...@ea...> - 2003-10-28 07:37:12
|
I'm still working and came across something very strange. When inserting a new survey in the DB (INSERT INTO survey ...), ODBC _does_ insert the new row in the survey table successfully BUT complains about "duplicate keys" (there are clearly no such duplicates). This happens when I do a sequence of odbc_prepare/odbc_execute statement. However, if I use an odbc_exec (which automatically does the prepare), everything is just fine. I'm clueless. To say it more technically, odbc_execute( odbc_prepare( $sql)) seems diffferent of odbc_exec( $sql). I'll try to dig the PHP source if I find some spare time... stF |