phpesp-devel — Discussion of the development of phpESP

Re: [phpesp-dev] Requirements: skip patterns/respondents/reports

[Matthew G. <gr...@mu...>]

On Wed, Oct 01, 2003 at 11:54:10AM -0600, Charlie Smith wrote:
> Can phpESP handle following.  If not do we have plans to do any of these types of things?
> 
> 1. Skip capabillities/paterns.  Ex.  User is redirected to different part of survey based on answer to question.
I patch exists to do this.  It has some problems and needs to be
cleaned up before it would be usable in production.
see -> http://bfs.itlab.musc.edu/~greggmc/stuff/newfork.patch

> 
> 2. How to handle people that drop out of survey early?
>    a.  If browser is killed
A survey can be setup so that a user can "suspend" a long survey and
return later to finish.

>    b. If user hits submit prematurely.
Not sure I under stand submitting prematurely?  You can designate
questions as required, so a user cannot submit until the required
questions are answered.


> 
> 3. How is final data presented?
>   Can we print reports vs. just a print screen?
You can see what reporting is available inside ESP, if other reporting
is needed, you would need to CSV export and generate the reports yourself.

> 
> 4. Can we track who's taken a given survey?   
> 
Yes.  Look at the private survey options.

> 5. email notifications to people who haven't taken survey possble?
> 
No

> 
> This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed.
> 
> 
> ==============================================================================
> 
> 
> 
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
> 

-- 
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)

[phpesp-dev] Styles

[Stefan C. <sch...@ea...>]

If I have time, I think it'd be nice to move all the HTML style coding to CSS. 
It'd be so much easier to ensure a coherent look all over the place.

stF

[phpesp-dev] Little things

[Stefan C. <sch...@ea...>]

I've noticed that sometimes one says :

- a "realm" when he means a "group"
- a "field" for a "question"
- a "form" for a "survey"

I'll fix them as I get them. If you agree, let's be consistent : 

- respondent : someone who answers a survey
- designer :  someone who makes a survey
- survey : a survey
- question : a question, part of a survey
- group : a set of people or a set of survey

stF

[phpesp-dev] Pick a survey

[Stefan C. <sch...@ea...>]

Every here and there, there is a possibility to pick a survey (fro reporting, 
testing, etc.)

I think that the list provided gives too much information. A "dumb" enduser 
doesn't care about a survey ID. Similarly, I don't see the point to give the 
group/owner name, if someone has no right to see someone else's work, that 
is, he'll just see his stuff.

So, I propose to simplify and abstract the "pick a survey" screens. I'll 
retain the original layout if the user is a "superuser". In that case, it is 
normal to provide as much information as possible.

stF

[phpesp-dev] Requirements: skip patterns/respondents/reports

[Charlie S. <Sm...@ld...>]

Can phpESP handle following.  If not do we have plans to do any of these =
types of things?

1. Skip capabillities/paterns.  Ex.  User is redirected to different part o=
=66=
 survey based on answer to question.

2. How to handle people that drop out of survey early?
   a.  If browser is killed
   b. If user hits submit prematurely.

3. How is final data presented?
  Can we print reports vs. just a print screen?

4. Can we track who's taken a given survey?  =20

5. email notifications to people who haven't taken survey possble?


---------------------------------------------------------------------------=
---
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

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Charlie S. <Sm...@ld...>]

I would also think we'd separate DB schema/scripts/logs for each database =
type.
The use of the ENUM type in mysql vs a check constraint in Oracle vs ? in =
PostGreSQL.

I would also advocate tying down the schema before proceeding with a rewrite
of phpESP to accomodate PEAR DB.   After the schema is tied down, we could =
delve into=20
translating the mysql calls to the PEARDB calls, and proceed with unit =
testing, if that sounds ok to=20
you guys.

I've written a perl script that reads from a sqldump/export from phpMyAdmin
and creates an Oracle schema for all the tables, triggers, indexes, =
sequencers.
So making modifications to what we want to do with the Oracle schema should
be fairly easy to make for all the tables.

I've also written a perl script to translate mysql function calls to =
routines I've written, which in turn make calls to OCI8/Oracle.  This scrip=
t=
 can be modified to translate the mysql functions to the =
PEARDB/MDB::functions().   We'll need to identify a PEARDB function for eac=
h=
 of the mysql functions that we have in the code, and identify any =
additional fields that would be needed.


With that:  =20
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




>>> "Matthew Gregg" <gr...@mu...> 09/30/03 11:19AM >>>
Probably going to have to create/maintain DB creation scripts for each
DB we plan on supporting.  Changes made to ESP also should be done in
a way that supports the all "supported" DB's.  With mySQL as a given, I
would target Postgres and Oracle as the supported databases.

On Tue, Sep 30, 2003 at 09:56:26AM -0700, Jeremy Buchmann wrote:
> I can start fairly soon, assuming we decide to use phpESP.  One thing I=20
> noticed right away was the database creation scripts.  Are we going to=20
> write one for each database we want to support, or is there some way to=20
> generically specify a database design?  One thing that caught my eye=20
> was the use of the ENUM type which is common in mySQL, but doesn't=20
> exist is PostgreSQL.  However, it looks like all the ENUMs just hold=20
> two values, Y and N, which would map to the boolean type (true,false)=20
> in PostgreSQL.  This will also affect the code, so I think it's=20
> something we should work out sooner rather than later.
>=20
>=20
> On Tuesday, September 30, 2003, at 07:27 AM, Charlie Smith wrote:
>=20
> >Looks like Jeremy Buchmann and I (Charlie Smith) could work on the=20
> >PEAR port right away.   Could we discuss this possibility?
> >
> >>>>"Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
> >http://pear.php.net=20
> >On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
> >>Where is the API located for PEAR?
> >>
> >>Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in=20
> >>an effort to port to PEAR compliant DB?
> >>
> >>I've a question with regards to how the NOT NULL default '' fields=20
> >>would be defined in the PEAR description?
> >>I'd be inclined to define these types of fieds as NOT NULL in Oracle=20
> >>and let the code or a trigger fill in the value
> >>with something if needed.   Any opinions?
> >>
> >>I'm sorry, I'm not familiar with the PEAR API.  Is this just a=20
> >>supporting library of php code?
> >>
> >>
> >>
> >>>>>"Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
> >>Hi all,
> >>
> >>I'm evaluating the use of phpESP for my company and have a few quick
> >>questions.
> >>
> >>First, we use PostgreSQL for all our database needs.  Since phpESP=20
> >>uses
> >>mySQL, we would either have to port it to PostgreSQL or assist in the
> >>port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on
> >>the number of lines in the code base that have 'mysql' in them, that I
> >>could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from
> >>the main distribution, so ideally I'd like to help in the port to=20
> >>PEAR,
> >>but I've never used PEAR.  With a quick glance at the API, it looks
> >>easy enough...fairly similar to Perl's DBI.  So my questions are, how
> >>is the PEAR port coming along?  Would my help be welcome and useful?
> >>Would phpESP only use the database parts of PEAR?
> >>
> >>Thanks,
> >>Jeremy
> >>
>=20
>=20
>=20
> 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
>=20

--=20
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)


-------------------------------------------------------
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

Re: [phpesp-dev] Translations

[Matthew G. <gr...@mu...>]

Yup, translations are going to be a pain.

Do the PEAR port first, basing it on the CVS phpESP code, before making any other
changes to phpESP.  That way it can be used by the community.

On Tue, Sep 30, 2003 at 10:23:04AM +0000, Stefan Champailler wrote:
> It looks difficult to add translation capabilities to phpESP.
> I've evaluated several scenarios but I'm quite disappointed overall.
> 
> My best try is to mark a survey as a "model" and make copies of, marked as 
> "localisations". Copies are independant (thus there's a risk of discrepancies 
> with the model).
> 
> From the acl point of view, we have : 
> 
> - Model belongs to one group, one designer.
> - Models are viewable for a given set of groups (those wich are going to 
> translate)
> - A translation is a copy of a model, owned by the translator and kept inside 
> the group of the translator.
> - The memeber of the group of the model have access to the copies (and only 
> the copies), even if they are outside the group.
> 
> I don't like this scenario because it breaks the idea that groups are private 
> (you are only allowed to see the surveys that are in you group). A nice 
> solution would be to allow that a person can belong to several groups. But 
> this require a lot of code refactoring.
> 
> I'd like to have your ideas here, because if I'm going to make big changes,it 
> is likely that my Pear port will be useless to the community. A bad thing.
> 
> stF
> 
> 
> 
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
> 

-- 
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)

[phpesp-dev] [ phpesp-Bugs-748223 ] CSV Export field name clash

[SourceForge.net <no...@so...>]

Bugs item #748223, was opened at 2003-06-03 09:53
Message generated for change (Comment added) made by greggmc
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

Category: Admin
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthew Gregg (greggmc)
Assigned to: Nobody/Anonymous (nobody)
Summary: CSV Export field name clash

Initial Comment:
CVS exporter doesn't  distinguish between fields that

are named the same.

----------------------------------------------------------------------

>Comment By: Matthew Gregg (greggmc)
Date: 2003-10-01 08:23

Message:
Logged In: YES 
user_id=14116

If the patch works for existing surveys it should go into

the tree.   Why would we want this optional?  Don't want to

have to ask people to apply a patch and we don't want to

continually keep the patch in sync with the tree.

----------------------------------------------------------------------

Comment By: Kon Angelopoulos (angek)
Date: 2003-10-01 06:50

Message:
Logged In: YES 
user_id=198398

I've tested it an it doesn't break existing surveys it only

applies to any new questions being added to the survey.

However how about distributing a patch that can be used by

those who find themselves in this situation where the

question id is joined to the question name thus making it

unique. They can then simply download the results again and

hopefully the problem no longer exists.

----------------------------------------------------------------------

Comment By: Matthew Gregg (greggmc)
Date: 2003-09-29 10:20

Message:
Logged In: YES 
user_id=14116

I think disallowing duplicate question names is the way to

go, but could break existing surveys.   How should we handle

that?  

----------------------------------------------------------------------

Comment By: Kon Angelopoulos (angek)
Date: 2003-09-27 20:25

Message:
Logged In: YES 
user_id=198398

I've added code to survey_update to prevent duplicate

question names from being used in a given survey which will

prevent this type of bug from reoccuring. If you think that

this is satisfactory then close this request.

If however you feel strongly about allowing duplicate names

and that the fix should be in the cvs export function then

please let me know and I'll look into it while I have a bit

of time on my hands.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

[phpesp-dev] [ phpesp-Bugs-748223 ] CSV Export field name clash

[SourceForge.net <no...@so...>]

Bugs item #748223, was opened at 2003-06-04 00:53
Message generated for change (Comment added) made by angek
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

Category: Admin
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthew Gregg (greggmc)
Assigned to: Nobody/Anonymous (nobody)
Summary: CSV Export field name clash

Initial Comment:
CVS exporter doesn't  distinguish between fields that

are named the same.

----------------------------------------------------------------------

>Comment By: Kon Angelopoulos (angek)
Date: 2003-10-01 21:50

Message:
Logged In: YES 
user_id=198398

I've tested it an it doesn't break existing surveys it only

applies to any new questions being added to the survey.

However how about distributing a patch that can be used by

those who find themselves in this situation where the

question id is joined to the question name thus making it

unique. They can then simply download the results again and

hopefully the problem no longer exists.

----------------------------------------------------------------------

Comment By: Matthew Gregg (greggmc)
Date: 2003-09-30 01:20

Message:
Logged In: YES 
user_id=14116

I think disallowing duplicate question names is the way to

go, but could break existing surveys.   How should we handle

that?  

----------------------------------------------------------------------

Comment By: Kon Angelopoulos (angek)
Date: 2003-09-28 11:25

Message:
Logged In: YES 
user_id=198398

I've added code to survey_update to prevent duplicate

question names from being used in a given survey which will

prevent this type of bug from reoccuring. If you think that

this is satisfactory then close this request.

If however you feel strongly about allowing duplicate names

and that the fix should be in the cvs export function then

please let me know and I'll look into it while I have a bit

of time on my hands.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Stefan C. <sch...@ea...>]

Hmmm...

I'm going to work on the port anytime soon, but it will be during next week. I 
think that if we are to work together, we have to share the work and follow a 
guideline.

It seems to me that the closer we stay to the original code, the better. 
Indeed, it's less modofication and, also, since we know where each existing 
MySQL statement is, it's easier to share the work. For example, I can do 
"edit.inc". Or if we happen to work on the same file, we have a common ground 
that will help us to merge our changes more easilly.

Stefan.



> You guys should work together and send the patches to the list.
> It would be best to patch against cvs.
>
> On Tue, Sep 30, 2003 at 08:27:44AM -0600, Charlie Smith wrote:
> > Looks like Jeremy Buchmann and I (Charlie Smith) could work on the PEAR
> > port right away.   Could we discuss this possibility?
> >
> > >>> "Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
> >
> > http://pear.php.net
> >
> > On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
> > > Where is the API located for PEAR?
> > >
> > > Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in an
> > > effort to port to PEAR compliant DB?
> > >
> > > I've a question with regards to how the NOT NULL default '' fields
> > > would be defined in the PEAR description? I'd be inclined to define
> > > these types of fieds as NOT NULL in Oracle and let the code or a
> > > trigger fill in the value with something if needed.   Any opinions?
> > >
> > > I'm sorry, I'm not familiar with the PEAR API.  Is this just a
> > > supporting library of php code?
> > >
> > > >>> "Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
> > >
> > > Hi all,
> > >
> > > I'm evaluating the use of phpESP for my company and have a few quick
> > > questions.
> > >
> > > First, we use PostgreSQL for all our database needs.  Since phpESP uses
> > > mySQL, we would either have to port it to PostgreSQL or assist in the
> > > port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on
> > > the number of lines in the code base that have 'mysql' in them, that I
> > > could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from
> > > the main distribution, so ideally I'd like to help in the port to PEAR,
> > > but I've never used PEAR.  With a quick glance at the API, it looks
> > > easy enough...fairly similar to Perl's DBI.  So my questions are, how
> > > is the PEAR port coming along?  Would my help be welcome and useful?
> > > Would phpESP only use the database parts of PEAR?
> > >
> > > Thanks,
> > > Jeremy
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > 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.
> > >
> > >
> > > =======================================================================
> > >=======
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > phpESP-devel mailing list
> > > php...@li...
> > > https://lists.sourceforge.net/lists/listinfo/phpesp-devel
> >
> > --
> > mcg
> > -------------------------------------
> > The IT Lab (http://www.itlab.musc.edu)
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > 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.
> >
> >
> > =========================================================================
> >=====
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > phpESP-devel mailing list
> > php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel

[phpesp-dev] Translations

[Stefan C. <sch...@ea...>]

It looks difficult to add translation capabilities to phpESP.
I've evaluated several scenarios but I'm quite disappointed overall.

My best try is to mark a survey as a "model" and make copies of, marked as=
=20
"localisations". Copies are independant (thus there's a risk of discrepanci=
es=20
with the model).

=46rom the acl point of view, we have :=20

=2D Model belongs to one group, one designer.
=2D Models are viewable for a given set of groups (those wich are going to=
=20
translate)
=2D A translation is a copy of a model, owned by the translator and kept in=
side=20
the group of the translator.
=2D The memeber of the group of the model have access to the copies (and on=
ly=20
the copies), even if they are outside the group.

I don't like this scenario because it breaks the idea that groups are priva=
te=20
(you are only allowed to see the surveys that are in you group). A nice=20
solution would be to allow that a person can belong to several groups. But=
=20
this require a lot of code refactoring.

I'd like to have your ideas here, because if I'm going to make big changes,=
it=20
is likely that my Pear port will be useless to the community. A bad thing.

stF

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Matthew G. <gr...@mu...>]

Probably going to have to create/maintain DB creation scripts for each
DB we plan on supporting.  Changes made to ESP also should be done in
a way that supports the all "supported" DB's.  With mySQL as a given, I
would target Postgres and Oracle as the supported databases.

On Tue, Sep 30, 2003 at 09:56:26AM -0700, Jeremy Buchmann wrote:
> I can start fairly soon, assuming we decide to use phpESP.  One thing I 
> noticed right away was the database creation scripts.  Are we going to 
> write one for each database we want to support, or is there some way to 
> generically specify a database design?  One thing that caught my eye 
> was the use of the ENUM type which is common in mySQL, but doesn't 
> exist is PostgreSQL.  However, it looks like all the ENUMs just hold 
> two values, Y and N, which would map to the boolean type (true,false) 
> in PostgreSQL.  This will also affect the code, so I think it's 
> something we should work out sooner rather than later.
> 
> 
> On Tuesday, September 30, 2003, at 07:27 AM, Charlie Smith wrote:
> 
> >Looks like Jeremy Buchmann and I (Charlie Smith) could work on the 
> >PEAR port right away.   Could we discuss this possibility?
> >
> >>>>"Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
> >http://pear.php.net
> >On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
> >>Where is the API located for PEAR?
> >>
> >>Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in 
> >>an effort to port to PEAR compliant DB?
> >>
> >>I've a question with regards to how the NOT NULL default '' fields 
> >>would be defined in the PEAR description?
> >>I'd be inclined to define these types of fieds as NOT NULL in Oracle 
> >>and let the code or a trigger fill in the value
> >>with something if needed.   Any opinions?
> >>
> >>I'm sorry, I'm not familiar with the PEAR API.  Is this just a 
> >>supporting library of php code?
> >>
> >>
> >>
> >>>>>"Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
> >>Hi all,
> >>
> >>I'm evaluating the use of phpESP for my company and have a few quick
> >>questions.
> >>
> >>First, we use PostgreSQL for all our database needs.  Since phpESP 
> >>uses
> >>mySQL, we would either have to port it to PostgreSQL or assist in the
> >>port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on
> >>the number of lines in the code base that have 'mysql' in them, that I
> >>could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from
> >>the main distribution, so ideally I'd like to help in the port to 
> >>PEAR,
> >>but I've never used PEAR.  With a quick glance at the API, it looks
> >>easy enough...fairly similar to Perl's DBI.  So my questions are, how
> >>is the PEAR port coming along?  Would my help be welcome and useful?
> >>Would phpESP only use the database parts of PEAR?
> >>
> >>Thanks,
> >>Jeremy
> >>
> 
> 
> 
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
> 

-- 
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Jeremy B. <je...@we...>]

I can start fairly soon, assuming we decide to use phpESP.  One thing I 
noticed right away was the database creation scripts.  Are we going to 
write one for each database we want to support, or is there some way to 
generically specify a database design?  One thing that caught my eye 
was the use of the ENUM type which is common in mySQL, but doesn't 
exist is PostgreSQL.  However, it looks like all the ENUMs just hold 
two values, Y and N, which would map to the boolean type (true,false) 
in PostgreSQL.  This will also affect the code, so I think it's 
something we should work out sooner rather than later.

--Jeremy

On Tuesday, September 30, 2003, at 07:27 AM, Charlie Smith wrote:

> Looks like Jeremy Buchmann and I (Charlie Smith) could work on the 
> PEAR port right away.   Could we discuss this possibility?
>
>>>> "Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
> http://pear.php.net
> On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
>> Where is the API located for PEAR?
>>
>> Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in 
>> an effort to port to PEAR compliant DB?
>>
>> I've a question with regards to how the NOT NULL default '' fields 
>> would be defined in the PEAR description?
>> I'd be inclined to define these types of fieds as NOT NULL in Oracle 
>> and let the code or a trigger fill in the value
>> with something if needed.   Any opinions?
>>
>> I'm sorry, I'm not familiar with the PEAR API.  Is this just a 
>> supporting library of php code?
>>
>>
>>
>>>>> "Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
>> Hi all,
>>
>> I'm evaluating the use of phpESP for my company and have a few quick
>> questions.
>>
>> First, we use PostgreSQL for all our database needs.  Since phpESP 
>> uses
>> mySQL, we would either have to port it to PostgreSQL or assist in the
>> port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on
>> the number of lines in the code base that have 'mysql' in them, that I
>> could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from
>> the main distribution, so ideally I'd like to help in the port to 
>> PEAR,
>> but I've never used PEAR.  With a quick glance at the API, it looks
>> easy enough...fairly similar to Perl's DBI.  So my questions are, how
>> is the PEAR port coming along?  Would my help be welcome and useful?
>> Would phpESP only use the database parts of PEAR?
>>
>> Thanks,
>> Jeremy
>>

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Christopher Z. <zo...@mu...>]

You guys should work together and send the patches to the list. 
It would be best to patch against cvs. 

On Tue, Sep 30, 2003 at 08:27:44AM -0600, Charlie Smith wrote:
> Looks like Jeremy Buchmann and I (Charlie Smith) could work on the PEAR port right away.   Could we discuss this possibility?
> 
> >>> "Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
> http://pear.php.net 
> On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
> > Where is the API located for PEAR?
> > 
> > Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in an effort to port to PEAR compliant DB?
> > 
> > I've a question with regards to how the NOT NULL default '' fields would be defined in the PEAR description?
> > I'd be inclined to define these types of fieds as NOT NULL in Oracle and let the code or a trigger fill in the value
> > with something if needed.   Any opinions?
> > 
> > I'm sorry, I'm not familiar with the PEAR API.  Is this just a supporting library of php code?
> > 
> > 
> > 
> > >>> "Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
> > Hi all,
> > 
> > I'm evaluating the use of phpESP for my company and have a few quick 
> > questions.
> > 
> > First, we use PostgreSQL for all our database needs.  Since phpESP uses 
> > mySQL, we would either have to port it to PostgreSQL or assist in the 
> > port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on 
> > the number of lines in the code base that have 'mysql' in them, that I 
> > could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from 
> > the main distribution, so ideally I'd like to help in the port to PEAR, 
> > but I've never used PEAR.  With a quick glance at the API, it looks 
> > easy enough...fairly similar to Perl's DBI.  So my questions are, how 
> > is the PEAR port coming along?  Would my help be welcome and useful?  
> > Would phpESP only use the database parts of PEAR?
> > 
> > Thanks,
> > Jeremy
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf 
> > _______________________________________________
> > 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.
> > 
> > 
> > ==============================================================================
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf 
> > _______________________________________________
> > phpESP-devel mailing list
> > php...@li... 
> > https://lists.sourceforge.net/lists/listinfo/phpesp-devel 
> -- 
> mcg
> -------------------------------------
> The IT Lab (http://www.itlab.musc.edu)
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf 
> _______________________________________________
> 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.
> 
> 
> ==============================================================================
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
> 

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Charlie S. <Sm...@ld...>]

Looks like Jeremy Buchmann and I (Charlie Smith) could work on the PEAR por=
t=
 right away.   Could we discuss this possibility?

>>> "Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
http://pear.php.net=20
On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
> Where is the API located for PEAR?
>=20
> Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in an =
effort to port to PEAR compliant DB?
>=20
> I've a question with regards to how the NOT NULL default '' fields would =
be defined in the PEAR description?
> I'd be inclined to define these types of fieds as NOT NULL in Oracle and =
let the code or a trigger fill in the value
> with something if needed.   Any opinions?
>=20
> I'm sorry, I'm not familiar with the PEAR API.  Is this just a supporting=
 =
library of php code?
>=20
>=20
>=20
> >>> "Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
> Hi all,
>=20
> I'm evaluating the use of phpESP for my company and have a few quick=20
> questions.
>=20
> First, we use PostgreSQL for all our database needs.  Since phpESP uses=20
> mySQL, we would either have to port it to PostgreSQL or assist in the=20
> port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on=20
> the number of lines in the code base that have 'mysql' in them, that I=20
> could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from=20
> the main distribution, so ideally I'd like to help in the port to PEAR,=20
> but I've never used PEAR.  With a quick glance at the API, it looks=20
> easy enough...fairly similar to Perl's DBI.  So my questions are, how=20
> is the PEAR port coming along?  Would my help be welcome and useful? =20
> Would phpESP only use the database parts of PEAR?
>=20
> Thanks,
> Jeremy
>=20
>=20
>=20
> -------------------------------------------------------
> 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
>=20
>=20
>=20
> =
---------------------------------------------------------------------------=
---
> This message may contain confidential information, and is intended only =
=66or the use of the individual(s) to whom it is addressed.
>=20
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>=20
>=20
>=20
> -------------------------------------------------------
> 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
--=20
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)



-------------------------------------------------------
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

Re: [phpesp-dev] ODBC support rewrite

[Charlie S. <Sm...@ld...>]

I just noticed the PEAR supported databases are listed as follows at =
pear.php.net. See =
http://pear.php.net/manual/en/package.database.mdb.intro-dsn.php
mysql  -> MySQL
pgsql  -> PostgreSQL
ibase  -> InterBase
mssql  -> Microsoft SQL Server
oci8   -> Oracle 7/8/8i
=66bsql  -> FrontBase

Stephan indicates that he prefers ODBC over PEAR because of poor benchmarks=
,=
 but it looks like
he's going to do a pear port anyway:  He stated:
"... Here's what I'll do=20
: as soon as I got a dev environment with Oracle/ODBC running, I'll test th=
e=
=20
Pear connectivity. If it works, I'll move my phpEsp to PEAR. But,=20
unfortunatley, I have also several additional features that I have to add t=
o=
=20
the code that are not necessarily good for everyone ..."

However, I'll need to interface with OCI8 right away.   Would it be =
beneficial for me to get started on a PEAR port?   I need to get phpESP =
going with OCI8 anyway - and right now.
Where are the benchmarks and what kind of time frame are we looking at to =
get the PEAR stuff done with Stephan doing it?



>>> "Matthew Gregg" <gr...@mu...> 09/25/03 07:59AM >>>
Why I favor Pear...
PearDB currently supports:
MySQL
PostgreSQL
InterBase
Mini SQL
Microsoft SQL Server
Oracle 7/8/8i
ODBC (Open Database Connectivity)
SyBase
Informix
=46rontBase

A port to PearDB will give us connectivity to all of these DB's almost
=66or free.  And I'm sure more thought and development time has gone
into these libraries that we would ever do in a generic solution.

How does a "generic" solution give us more choice?


On Thu, Sep 25, 2003 at 06:46:34PM +1000, Kon wrote:
> Guys,
>=20
> I think that the generic functions would be OK as it provides greater
> choice.
>=20
> Regards
>=20
> Kon
>=20
>=20
> On Thu, 2003-09-25 at 04:04, Matthew Gregg wrote:
> > I would prefer a PEAR solution, but something like this would be ok.
> >=20
> > On Wed, Sep 24, 2003 at 11:59:32AM -0600, Charlie Smith wrote:
> > > So instead of mysql_connect or @OCIPLogon($oracleUser, =
$oraclePassword, $oracleSid);
> > > you could have:
> > >=20
> > > function genDBConnect($genDBSid, $genDBUser, $genDBPassword) {
> > >   if (DB =3D=3D 'Oracle) {
> > >       $connected =3D @OCIPLogon($genDBUser, $genDBPassword, =
$genDBSid);
> > >=20
> > >       if($error =3D OCIError()) {
> > >         die("<font color=3Dred>ERROR!! Couldn't connect to =
server!</font>");
> > >       }
> > >       return $connected;
> > >   }
> > >   else if (DB =3D=3D 'MySQL' {
> > >       mysql_connect($genDBSid, $genDBUser, $genDBPassword)
> > >   }
> > > }
> > >=20
> > > Something like this?  along with other generic functions to handle =
each of the mysql/oracle functional pieces?
> > >=20
> > >=20
> > > >>> "Matthew Gregg" <gr...@mu...> 09/24/03 10:56AM >>>
> > > This does sound good.  But instead of porting to Oracle, a port to
> > > PEAR or some other "generic" database abstraction layer would be even
> > > better.
> > >=20
> > > On Wed, Sep 24, 2003 at 09:38:28AM -0600, Charlie Smith wrote:
> > > > I'm starting a project to give us an oracle interface ie. replacing=
 =
mySQL calls with Oracle.  Sounds like this could be beneficial to others, =
especially you.   Hope to be done by end of  day today.  Will let you know =
if sounds good to you.
> > > >=20
> > > > >>> "Stefan Champailler" <sch...@ea...> 09/22/03 08:09AM=
 =
>>>
> > > > Dear all,
> > > >=20
> > > >=20
> > > > I'm going to use phpESP for a project inside a big tyre company. =
However, I'll=20
> > > > need to interface it with Oracle through ODBC. So, what do you thin=
k=
 is=20
> > > > better :
> > > >=20
> > > > - use normal ODBC (iODBC, unixODBC)
> > > > - use PEAR libs
> > > >=20
> > > > Personally, I prefer ODBC because I read very poor benchmarks for =
PEAR=20
> > > > database access.
> > > >=20
> > > > Any suggestions ?
> > > >=20
> > > > Stefan
> > > >=20
> > > >=20
> > > >=20
> > > > 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
> > > >=20
> > > >=20
> > > >=20
> > > > This message may contain confidential information, and is intended =
only for the use of the individual(s) to whom it is addressed.
> > > >=20
> > > >=20
> > > > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> > > >=20
> > > >=20
> > > >=20
> > > > 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
> > > >=20
> > >=20
>=20

--=20
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)


-------------------------------------------------------
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

Re: [phpesp-dev] ODBC support rewrite

[Stefan C. <sch...@ea...>]

> Attached are scripts to use in creating Oracle tables

Cool ! As soon as I start my Pear port, the information you provide here will 
be very helpful !

stF

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Matthew G. <gr...@mu...>]

http://pear.php.net
On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
> Where is the API located for PEAR?
> 
> Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in an effort to port to PEAR compliant DB?
> 
> I've a question with regards to how the NOT NULL default '' fields would be defined in the PEAR description?
> I'd be inclined to define these types of fieds as NOT NULL in Oracle and let the code or a trigger fill in the value
> with something if needed.   Any opinions?
> 
> I'm sorry, I'm not familiar with the PEAR API.  Is this just a supporting library of php code?
> 
> 
> 
> >>> "Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
> Hi all,
> 
> I'm evaluating the use of phpESP for my company and have a few quick 
> questions.
> 
> First, we use PostgreSQL for all our database needs.  Since phpESP uses 
> mySQL, we would either have to port it to PostgreSQL or assist in the 
> port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on 
> the number of lines in the code base that have 'mysql' in them, that I 
> could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from 
> the main distribution, so ideally I'd like to help in the port to PEAR, 
> but I've never used PEAR.  With a quick glance at the API, it looks 
> easy enough...fairly similar to Perl's DBI.  So my questions are, how 
> is the PEAR port coming along?  Would my help be welcome and useful?  
> Would phpESP only use the database parts of PEAR?
> 
> Thanks,
> Jeremy
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> 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.
> 
> 
> ==============================================================================
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
-- 
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)

[phpesp-dev] [ phpesp-Bugs-748223 ] CSV Export field name clash

[SourceForge.net <no...@so...>]

Bugs item #748223, was opened at 2003-06-03 09:53
Message generated for change (Comment added) made by greggmc
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

Category: Admin
Group: None
>Status: Open
Resolution: None
Priority: 5
Submitted By: Matthew Gregg (greggmc)
Assigned to: Nobody/Anonymous (nobody)
Summary: CSV Export field name clash

Initial Comment:
CVS exporter doesn't  distinguish between fields that

are named the same.

----------------------------------------------------------------------

>Comment By: Matthew Gregg (greggmc)
Date: 2003-09-29 10:20

Message:
Logged In: YES 
user_id=14116

I think disallowing duplicate question names is the way to

go, but could break existing surveys.   How should we handle

that?  

----------------------------------------------------------------------

Comment By: Kon Angelopoulos (angek)
Date: 2003-09-27 20:25

Message:
Logged In: YES 
user_id=198398

I've added code to survey_update to prevent duplicate

question names from being used in a given survey which will

prevent this type of bug from reoccuring. If you think that

this is satisfactory then close this request.

If however you feel strongly about allowing duplicate names

and that the fix should be in the cvs export function then

please let me know and I'll look into it while I have a bit

of time on my hands.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Charlie S. <Sm...@ld...>]

Where is the API located for PEAR?

Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in an =
effort to port to PEAR compliant DB?

I've a question with regards to how the NOT NULL default '' fields would be=
 =
defined in the PEAR description?
I'd be inclined to define these types of fieds as NOT NULL in Oracle and le=
t=
 the code or a trigger fill in the value
with something if needed.   Any opinions?

I'm sorry, I'm not familiar with the PEAR API.  Is this just a supporting =
library of php code?



>>> "Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
Hi all,

I'm evaluating the use of phpESP for my company and have a few quick=20
questions.

=46irst, we use PostgreSQL for all our database needs.  Since phpESP uses=20
mySQL, we would either have to port it to PostgreSQL or assist in the=20
port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on=20
the number of lines in the code base that have 'mysql' in them, that I=20
could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from=20
the main distribution, so ideally I'd like to help in the port to PEAR,=20
but I've never used PEAR.  With a quick glance at the API, it looks=20
easy enough...fairly similar to Perl's DBI.  So my questions are, how=20
is the PEAR port coming along?  Would my help be welcome and useful? =20
Would phpESP only use the database parts of PEAR?

Thanks,
Jeremy



-------------------------------------------------------
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

Re: [phpesp-dev] include/tab/questions.inc

[Stefan C. <sch...@ea...>]

Here is the source code of my modified version.
(sorry for being angry last time, but damn, it was just toooo harsh :))
:)

stF


<?php

# $Id: questions.inc,v 1.13 2003/03/05 19:26:38 jimmerman Exp $

// Written by James Flemer
// For eGrad2000.com
// <jf...@al...>
// Almost entirely rewritten by Stefan Champailler (for clarity)


/*
echo("\$HTTP_POST_VARS['q']=".$HTTP_POST_VARS['q']);
    // selected question number (1 is the first, n is the last)
echo(", \$HTTP_POST_VARS['id'] =".$HTTP_POST_VARS['id']);
    // question id ?
    // id is retransmitted each time the question edit is
    // submitted. what happens, if we're creating a new question
    // with errors in it, that is, one that hasn't any id.

echo(", \$HTTP_POST_VARS['type_id']=".$HTTP_POST_VARS['type_id']);
    // question type id
echo "<br>";

echo(", \$HTTP_SESSION_VARS['survey_id'] =".$HTTP_SESSION_VARS['survey_id']);
echo(", \$HTTP_SESSION_VARS['last_tab'] =". $HTTP_SESSION_VARS['last_tab']);
echo "<br>";
echo "\$updated ? $updated";

    // survey id.
    // In case of "edit a survey", survey_id is made out of newid in
    // tab.inc
*/


    /* Some constants that will soon be used */

    $FIELDS = 
array('name','type_id','length','precise','required','content','position');
        // Scary: name is not shown, but kept anyway... I made that to
        // avoid disrupting other code parts (esp. survey_update).

    $NEW_QUESTION_ID = "new_question_id";

    $NEW_QUESTION_BUTTON = _("New Field");

    // Sanitize
    if( empty( $HTTP_SESSION_VARS['survey_id']))
        trigger_error( _("Empty survey id. This can't happen."), 
E_USER_ERROR);

    /* $sid is a /shortcut/ to $HTTP_SE..., it shall not
       be modified. */

    $sid =& $HTTP_SESSION_VARS['survey_id'];

    /* We collect all the questions id's of the survey. This
       will soon be helpful. */

    $sql = "SELECT id FROM question WHERE survey_id='$sid' AND deleted='N'
            AND type_id != 99 ORDER BY position";
         // stF: 99 is page break
    $result = mysql_query($sql);
    $q_ids = array();
    while(list($qi) = mysql_fetch_row($result))
        array_push($q_ids, $qi);
    mysql_free_result($result);


    /* $HTTP_POST_VARS['id'] is the question we WERE working on
       at submission time
       and we'll set up $id which the question we ARE working
       on.*/

    $id = "!!!unset!!!";

    /* We define a little shortcut here ($q). Plese note that it preserves
       the nullity of POST_VAR[q] if necessary.  */

    $q='';

    $q_post = $HTTP_POST_VARS['q'];
    if( $q_post > 0 && $q_post <= count( $q_ids))
        $q = $q_post;
    elseif( !empty( $q_post))
        $q = $NEW_QUESTION_BUTTON;
    unset($q_post);


    /* So, now the whole job is to get $id from $HTTP_POST_VARS['q']
       and other things...

       When we say "were working on", it means that it was the
       id of the question that was displayed when the user submitted
       its modifications. The number of ways a page is submitted
       is given by the number of buttons on the page multiplied
       by the fact that the submission has or has not been
       accepted (because invallid values).

       Globally the schema is this :
         - we were editing $id, we clicked on something, our edition
           is valid and we can fall on the somthign that was selected.
         - we were not editing and we fall back where we should.
         - we were editing $id, we clicked on something, our edition
           is NOT valid and we must stay here. */

    /* So first question, where are we coming from */

    $coming_from_outside =
        $HTTP_SESSION_VARS['last_tab'] != 'questions';

    $submitted_data_are_valid =
        (empty($HTTP_POST_VARS['content']) && empty($HTTP_POST_VARS['name']))
        || $updated;;

    $request_for_new_question = $q == $NEW_QUESTION_BUTTON;
    $request_for_edit_question = $q > 0;

    $request_for_extra_choice = !empty($HTTP_POST_VARS['extra_choices']);

    $outside_requested_qid = -1;
    if( !$request_for_new_question && $q > 0) // So we avoid empty(q)
        $outside_requested_qid = $q_ids[ $q - 1];

/*
    echo "\$coming_from_outside = $coming_from_outside ";
    if( $coming_from_outside)
        echo "\$outside_requested_qid = $outside_requested_qid";
    echo "<br/>";

    echo "request_for_extra_choice = $request_for_extra_choice";
    echo "<br/>";
*/

    /* Now that we know where we're coming from, we can see if
       we can fulfill user's request (that is, go where he wants
       to go). */

    /* If true, then it's the first time that we display
       the form for the edited question.

       If false, it's not the first time, it means that the
       user has just submitted the question. */

    $ignore_post_var = false;

    if( $coming_from_outside) {
        /* As we're not coming from outside, we're not working
           on any particular question.
           Therefore, we have several possibilities :
              - There's no question to work on (creating a survey)
              - There's a question and we want to edit it.

           So, are we working with a survey that has some questions
           in it ? */

        if( count( $q_ids) > 0) {
            // Yes, at least one question.

            // Outside may have requested to work on a special question.
            if( $outside_requested_qid >= 0)
                $id = $outside_requested_qid;
             else
                // we decide to edit the first of the available questions.
                $id = $q_ids[0];
        } else {
            // No, we're creating a new question
            $id = $NEW_QUESTION_ID;
        }

        $ignore_post_var = true;

    } else {
        // Coming from the inside

        if( $submitted_data_are_valid) {

            if( $request_for_new_question) {
                $id = $NEW_QUESTION_ID;
                $ignore_post_var = true;
            }
            elseif( $request_for_edit_question) {
                $id = $q_ids[$HTTP_POST_VARS['q'] - 1];
                $ignore_post_var = true;
            }
            elseif( $request_for_extra_choice)
                $id = $HTTP_POST_VARS['id'];

        } else
            $id = $HTTP_POST_VARS['id'];
    }



    /* At this point, $id is in a defined state.
       That is, it is either a integer, representing
       an existing id, or it is set to $NEW_QUESTION_ID
       which means that we're
       editing a question that has still no ID (i.e. a
       new question) */

    if( $id != $NEW_QUESTION_ID
        && !in_array( $id, $q_ids))
            trigger_error( _("Unrecognized question id ($id)"), E_USER_ERROR);


    /* Now we are going to display the form. The job is to
       figure out the value of each of the field.
       The fields value are set/read in the HTPP_POST array.

       - If we're editing an existing question, then the values
       are to be taken from the HTTP_POST array.

       - If we're arriving on the edit screen for the first time
       (for an exisiting question),
       then the values are to be taken from the database.

       - If we're creating a new question, then all the fields
       are empty (and so are the HTTP_POST)

       - If we're editing a new question, then all the fields
       come from the HTTP_POST) */

    $multiple_choices = array();


    if( $ignore_post_var && $id == $NEW_QUESTION_ID) {

        // We clear, just to make sure that there's no garbage
        // in the POST vars.

        foreach($FIELDS as $f) unset( $HTTP_POST_VARS[$f]);

        for($i=0; $i<$GLOBALS['ESPCONFIG']['default_num_choices']; $i++)
            array_push( $multiple_choices, array( "id" => '', "content" => 
''));

        // We set some defaults

        $HTTP_POST_VARS['required'] = 'N';
        $HTTP_POST_VARS['type_id'] = 2;

    } elseif( $ignore_post_var && $id != $NEW_QUESTION_ID) {

        /* We load everything from the DB. */

        $sql = "SELECT * FROM question WHERE id='${id}' AND deleted='N'";
        $result = mysql_query($sql);
        $question = mysql_fetch_array($result,MYSQL_ASSOC);
        mysql_free_result($result);
        foreach($FIELDS as $f)
            $HTTP_POST_VARS[$f] = _stripslashes( $question[$f]);

        /* Load the multiple choices if it's relevant to this question. */

        if( esp_type_has_choices2( $HTTP_POST_VARS[type_id])) {
            $sql = "SELECT id,content FROM question_choice WHERE 
question_id='${id}' ORDER BY id";
            $result = mysql_query($sql);

            while( $a = mysql_fetch_assoc($result)) {
                $a['content'] = _stripslashes( $a['content']);
                array_push( $multiple_choices, $a);
            }
        }

    } else {
        /* Here, we have $ignore_post_var == false, so we have
           to take care of what the user submitted. */

        for( $i = 1; $i <= $HTTP_POST_VARS['num_choices']; $i++)
            array_push(
                $multiple_choices,
                array( 'id' => $HTTP_POST_VARS["choice_id_$i"],
                       'content' => $HTTP_POST_VARS["choice_content_$i"]));

        if( $request_for_extra_choice)
            array_push( $multiple_choices, array( "id" => '', "content" => 
''));
    }

    /* Now, we'd like to know what's the "number" of the question
       from the user point of view. If the question is new, we'll
       set it to false. Since it is user point of view, $q_number
       will be 1-based. */

    $q_number = false;
    if( $id != $NEW_QUESTION_ID)
        $q_number = array_search( $id, $q_ids) + 1;

    /* Now we set up an array with all the question types in it.
       99 is the page break that can be added in the Order tab. */

    $sql = 'SELECT id, type FROM question_type WHERE id != 99';
    $result = mysql_query($sql);
    $arr = array();
    while(list($key, $val) = mysql_fetch_row($result)) {
        $arr["$key"] = _($val);
    }

?>










<script language="javascript">
<!-- // comment
function clearTextInputs() {
    var i = 1;
    while (document.phpesp.elements["choice_content_" + i]) {
        document.phpesp.elements["choice_content_" + i].value = "";
        i++;

        }
}
// comment -->
</script>

    <input type="hidden" name="id" value="<?php echo($id); ?>">

    <p>
    <?php //echo(_('Edit this field, or click the number of the field you 
would like to edit:')); ?>
    </p>

    <table>
        <tr>
            <td colspan="2">
<?php


    // If == 0 it means we're working on a question that is not
    // in the DB, therefore a "new question"

    if( $id == $NEW_QUESTION_ID )
        echo _('You are currently editing a new question ');
    else
        echo _('You are currently editing question ') . "<b>$q_number</b>.";

?>
            </td>
        </tr>

        <tr>
            <td halign="left">
<?php
    if( count( $q_ids) > 0) {
        if( count( $q_ids) == 1)
            echo _("Question you can edit:");
        else
            echo _("Questions you can edit:");
?>
            </td>
            <td>
<?php
        for( $i=1; $i<=count( $q_ids); ++$i)
            if( $i != $q_number) {
        ?>
            <input type="submit" name="q" value="<?php echo($i); ?>">
        <?php
            } else
                echo("&nbsp;&nbsp;".$i."&nbsp;&nbsp;");
    }
?>
                <input type="submit" name="q" value="<?php 
echo($NEW_QUESTION_BUTTON); ?>">
            </td>
        </tr>
    </table>


    <hr>


    <table>

        <tr>
            <th><?php echo _('Type');?></th>
            <td><?php
                echo( mkselect('type_id',$arr, null, false));
            ?></td>
        </tr>

        <tr>
            <th><?php echo _('Required');?></th>
            <td>
            <?php
                echo(
                    mkselect( "required",
                              array("Y" => _('Yes'),"N" => _('No')),
                              null,
                              false)
                );
            ?></td>
        </tr>

        <tr>
            <th><?php echo _('Text');?></th>
            <td colspan="5" valign="top"><?php
                echo(mktextarea("content",4,60,"VIRTUAL"));
            ?></td>
        </tr>


<?php
    // has answer options ... so show that part of the form
    if( $id == $NEW_QUESTION_ID ||
        esp_type_has_choices2( $HTTP_POST_VARS[type_id])) {
?>
        <th>
            <?php echo _('Possible answers') ?>
        </th>

        <td>
            <input type="hidden" name="num_choices"
                   value="<?php echo(count($multiple_choices)); ?>">
<?php
            for($i=0; $i<count( $multiple_choices); $i++) {
?>
                <input type="hidden" name="choice_id_<?php echo($i+1); ?>"
                    value="<?php echo( $multiple_choices[$i]['id']); ?>">
                <input type="text" size="60" name="choice_content_<?php 
echo($i+1); ?>"
                    value="<?php echo( $multiple_choices[$i]['content']); ?>">
                <br/>

<?php        } ?>
        <br/>
        <input type="submit" name="extra_choices" value="<?php echo(_('Add 
another answer line')); ?>"> <input type="button" name="clear" value="Clear 
all answer lines" onClick="clearTextInputs()">
        </td>
<?php
    }
?>

    </table>

<hr/>

Re: [phpesp-dev] ODBC support rewrite

[Charlie S. <sm...@ld...>]

In attempting a conversion to Oracle, I've noticed that some fields are =
defined with NOT NULL default ''
=20
Oracle won't accept a "NOT NULL" and a default value.
Also the empty string ''   doesn't appear to be acceptable either.   The =
enum type would be translated to a check constraint and added after the =
table definition, as a lot of
the fields appear to be defined in mysql with a enum and default value.   =
Oracle doesn't like a check constraint and a default value in the actual =
table definition either, but works to have the check constraint defined by =
itself as follows.
=20
I wonder if I shouldn't leave the NOT NULL off of these field definitions =
where there is also a default values.  Also, it may easier to convert the =
code to use oracle if there were a space in place of the empty string?  Any=
 =
opinions?
=20
Ex.  This would be the table definition for the designer table:
drop table designer;
create table designer
(
username varchar2(64) default ' ',
password varchar2(16) default ' ',
auth varchar2(16) default 'BASIC',
realm varchar2(16) default ' ',
=66name varchar2(16) default NULL,
lname varchar2(24) default NULL,
email varchar2(64) default NULL,
pdesign  varchar2(7) default 'Y',
pstatus  varchar2(7) default 'N',
pdata  varchar2(7) default 'N',
pall  varchar2(7) default 'N',
pgroup  varchar2(7) default 'N',
puser  varchar2(7) default 'N',
disabled  varchar2(7) default 'N',
changed varchar2(14),
expiration varchar2(14)
)
tablespace users
storage (initial 2M next 2M);
=20
-- alter table designer drop constraint designer_pdesign_ck;
alter table designer
  add constraint designer_pdesign_ck
  check (pdesign in ('Y','N'));
=20
-- alter table designer drop constraint designer_pstatus_ck;
alter table designer
  add constraint designer_pstatus_ck
  check (pstatus in ('Y','N'));
=20
-- alter table designer drop constraint designer_pdata_ck;
alter table designer
  add constraint designer_pdata_ck
  check (pdata in ('Y','N'));
=20
-- alter table designer drop constraint designer_pall_ck;
alter table designer
  add constraint designer_pall_ck
  check (pall in ('Y','N'));
=20
-- alter table designer drop constraint designer_pgroup_ck;
alter table designer
  add constraint designer_pgroup_ck
  check (pgroup in ('Y','N'));
=20
-- alter table designer drop constraint designer_puser_ck;
alter table designer
  add constraint designer_puser_ck
  check (puser in ('Y','N'));
=20
-- alter table designer drop constraint designer_disabled_ck;
alter table designer
  add constraint designer_disabled_ck
  check (disabled in ('Y','N'));
=20
-- alter table designer drop Primary key cascade;
alter table designer
  add constraint designer_username_real_pk
  primary key (username,realm)
  using index;



>>> Kon <ang...@ip...> 09/25/03 02:46AM >>>
Guys,

I think that the generic functions would be OK as it provides greater
choice.

Regards

Kon


On Thu, 2003-09-25 at 04:04, Matthew Gregg wrote:
> I would prefer a PEAR solution, but something like this would be ok.
>=20
> On Wed, Sep 24, 2003 at 11:59:32AM -0600, Charlie Smith wrote:
> > So instead of mysql_connect or @OCIPLogon($oracleUser, $oraclePassword,=
 =
$oracleSid);
> > you could have:
> >=20
> > function genDBConnect($genDBSid, $genDBUser, $genDBPassword) {
> >   if (DB =3D=3D 'Oracle) {
> >       $connected =3D @OCIPLogon($genDBUser, $genDBPassword, $genDBSid);
> >=20
> >       if($error =3D OCIError()) {
> >         die("<font color=3Dred>ERROR!! Couldn't connect to =
server!</font>");
> >       }
> >       return $connected;
> >   }
> >   else if (DB =3D=3D 'MySQL' {
> >       mysql_connect($genDBSid, $genDBUser, $genDBPassword)
> >   }
> > }
> >=20
> > Something like this?  along with other generic functions to handle each=
 =
of the mysql/oracle functional pieces?
> >=20
> >=20
> > >>> "Matthew Gregg" <gr...@mu...> 09/24/03 10:56AM >>>
> > This does sound good.  But instead of porting to Oracle, a port to
> > PEAR or some other "generic" database abstraction layer would be even
> > better.
> >=20
> > On Wed, Sep 24, 2003 at 09:38:28AM -0600, Charlie Smith wrote:
> > > I'm starting a project to give us an oracle interface ie. replacing =
mySQL calls with Oracle.  Sounds like this could be beneficial to others, =
especially you.   Hope to be done by end of  day today.  Will let you know =
if sounds good to you.
> > >=20
> > > >>> "Stefan Champailler" <sch...@ea...> 09/22/03 08:09AM =
>>>
> > > Dear all,
> > >=20
> > >=20
> > > I'm going to use phpESP for a project inside a big tyre company. =
However, I'll=20
> > > need to interface it with Oracle through ODBC. So, what do you think =
is=20
> > > better :
> > >=20
> > > - use normal ODBC (iODBC, unixODBC)
> > > - use PEAR libs
> > >=20
> > > Personally, I prefer ODBC because I read very poor benchmarks for PEA=
R=
=20
> > > database access.
> > >=20
> > > Any suggestions ?
> > >=20
> > > Stefan
> > >=20
> > >=20
> > >=20
> > > 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
> > >=20
> > >=20
> > >=20
> > > This message may contain confidential information, and is intended =
only for the use of the individual(s) to whom it is addressed.
> > >=20
> > >=20
> > > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> > >=20
> > >=20
> > >=20
> > > 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
> > >=20
> >=20



-------------------------------------------------------
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

[phpesp-dev] [ phpesp-Bugs-748223 ] CSV Export field name clash

[SourceForge.net <no...@so...>]

Bugs item #748223, was opened at 2003-06-04 00:53
Message generated for change (Comment added) made by angek
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

Category: Admin
Group: None
>Status: Pending
Resolution: None
Priority: 5
Submitted By: Matthew Gregg (greggmc)
Assigned to: Nobody/Anonymous (nobody)
Summary: CSV Export field name clash

Initial Comment:
CVS exporter doesn't  distinguish between fields that

are named the same.

----------------------------------------------------------------------

>Comment By: Kon Angelopoulos (angek)
Date: 2003-09-28 11:25

Message:
Logged In: YES 
user_id=198398

I've added code to survey_update to prevent duplicate

question names from being used in a given survey which will

prevent this type of bug from reoccuring. If you think that

this is satisfactory then close this request.

If however you feel strongly about allowing duplicate names

and that the fix should be in the cvs export function then

please let me know and I'll look into it while I have a bit

of time on my hands.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=748223&group_id=8956

[phpesp-dev] [ phpesp-Bugs-789042 ] CSV Export field name clash 2

[SourceForge.net <no...@so...>]

Bugs item #789042, was opened at 2003-08-15 12:13
Message generated for change (Comment added) made by angek
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=789042&group_id=8956

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Paul Jackson (beachbum_boy)
Assigned to: Kon Angelopoulos (angek)
Summary: CSV Export field name clash 2

Initial Comment:
The CSV doesn't deal with questions with the same 

name (as mentioned in another bug report). 



But further to this if there is many fields with the same 

name the time to do the CSV export grows exponentially 

because of the way it handles quotes is majorly broken.



Basically each field gets a pair of quotes on either side 

for the csv export but because it actually keeps using 

the same field it gets more and more. And further to this 

the quotes are replaced via an ereg-replace with 2 

quotes. So this is fine when you have only a couple of 

questions with the same name but someone on our 

system had 60. Now the time to run this becomes 

untenable.



To see an example of this check out the results and 

survey on the demo site called csv_test.



I personally think the csv export stuff needs to be 

written from scratch again. Even when it works its very 

slow and hits the datbase way more than is really 

required if more complex sql was used.

----------------------------------------------------------------------

>Comment By: Kon Angelopoulos (angek)
Date: 2003-09-28 11:17

Message:
Logged In: YES 
user_id=198398

fixed in cvs.

survey question names are now checked for duplication.

----------------------------------------------------------------------

Comment By: Kon Angelopoulos (angek)
Date: 2003-09-26 14:00

Message:
Logged In: YES 
user_id=198398

will add some logic to check previous question names.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=789042&group_id=8956

Re: [phpesp-dev] ODBC support rewrite

[Charlie S. <Sm...@ld...>]

Attached are scripts to use in creating Oracle tables

Could someone look these over and see if they look ok.   I had to change a =
column name from public to public_esp
and a table name from access to access_esp as  'public' and 'access' are =
reserved words in Oracle.

Hope to have code ported over soon.

Previous email:

I'm starting a project to give us an oracle interface ie. replacing mySQL =
calls with Oracle.  Sounds like this could be beneficial to others, =
especially you.   Hope to be done by end of  day today.  Will let you know =
if sounds good to you.

>>> "Stefan Champailler" <sch...@ea...> 09/22/03 08:09AM >>>
Dear all,


I'm going to use phpESP for a project inside a big tyre company. However, =
I'll=20
need to interface it with Oracle through ODBC. So, what do you think is=20
better :

- use normal ODBC (iODBC, unixODBC)
- use PEAR libs

Personally, I prefer ODBC because I read very poor benchmarks for PEAR=20
database access.

Any suggestions ?

Stefan



-------------------------------------------------------
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