phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] One more thing

[Don S. <do...@se...>]

So the modules use the core's sqlInsert function for their own database 
transactions?

Don.

On Tue, 22 Oct 2002, Matthew McNaney wrote:

> I forgot to mention. You will need the core_sequence table.
> 
> Should install on setup. I have NOT removed the PEAR sequence from the
> setup yet so you will get the _seq tables. I will remove them when
> approved.
> 
> Matt
> 
> 
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> ICQ: 141057403
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of 
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
> program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 

[Phpwebsite-developers] One more thing

[Matthew M. <ma...@tu...>]

I forgot to mention. You will need the core_sequence table.

Should install on setup. I have NOT removed the PEAR sequence from the
setup yet so you will get the _seq tables. I will remove them when
approved.

Matt


Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403

[Phpwebsite-developers] sqlInsert rewrite

[Matthew M. <ma...@tu...>]

I rewrote the sqlInsert function this morning. Here is how it works:

When sqlInsert is requested, the insert table and the core_sequence table
are locked.

getSequence is called. It returns the next id of that table.

The table gets its insertion with the new ID. If successful, the sequence
table is updated.

Notes:

getSequence pulls the max id from the core.
The core sequence numbers are not populated until the first insert is called.
Deleting a row does not effect the sequence.
Inserting a row outside of sqlInsert will not effect the sequencing. It
makes sure that it is the highest number.
If the insert fails, the sequence is not updated.
The incrementing is invisible: you don't have to indicate the column to
increment any more.

I am going to commit the current version. It works with the exact same
parameters. I do want to change the parameters around however and remove
the idColumn row (it is no longer used) after approval by everyone.

Thanks,
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Adam M. <ad...@tu...>]

I'm with the single table idea for all sequence numbers.

This way we can have one select on init that loads all sequence numbers
into a session array.  Then on inserts we only have to update the
core_sequencer table instead of select AND update it (thinking of reducing
database accesses).

Also, with all the sequence numbers in the core table, we can get rid of
the current _seq tables getting our table total back down to around 23 :)
(organizational +).

Another plus? A quick re-write of the sqlmaxid function can simply return
the id in the sessioned sequence array (less database action=good...there
may be more functions that can take advantage).

We can continue to rely on the pear package, we just need to try and get
the best of all worlds.

Adam

---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Eloi G. <el...@re...>]

> Hmmm. There might be a way around this.
>
> Say we create our OWN sequencer.
>
> table : core_sequencer
> -----------------
> column : table_name
> column : primary_key_name
> column : current_id

Gotta give a -1 on this one.  While it is a really elegant solution to the
table spawn problem, it becomes a bottleneck when your site breaks into the
mainstream.  It's one thing when you have 20 queries + 5 inserts per second
on various tables in your database.  But if each of those inserts also
requires a table lock on the core_sequencer, the entire site will get bogged
down really fast.

I know I'm coming in too late in the game, but it'd be great if phpWS didn't
try to support every db in the known world.  That way there wouldn't be a
bunch of middle-layer generalized db access protocols to slow everything
down.

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Don S. <do...@se...>]

Although for what it's worth, my vote is still just to use the PEAR 
sequencer.  It is a "standard" of sorts.

Do modules go through the core sqlInsert function for their database 
transactions?

Don.

On Mon, 21 Oct 2002, Don Seiler wrote:

> I like this better than just selecting the max ID from the table and 
> incrementing.
> 
> I'm assuming you lock the sequencer table while incrementing?  If so is 
> there any chance of creating dead-locks on multiple inserts?
> 
> Don.
> 
> On Mon, 21 Oct 2002, Matthew McNaney wrote:
> 
> > 
> > > I would like to tak a closer look at the implemetation of this.  It
> > > looks like it's creating an extra table just to calculate the next
> > > sequence number.  Do you really want this since it could effectively
> > > double the amount of tables in the database?
> > 
> > Hmmm. There might be a way around this.
> > 
> > Say we create our OWN sequencer.
> > 
> > table : core_sequencer
> > -----------------
> > column : table_name
> > column : primary_key_name
> > column : current_id
> > 
> > When sqlImport calls "create table" with a primary key then the table name
> > and key are inserted into the sequencer.
> > 
> > Then when sqlInsert is called the table name is selected. The column name
> > and current id are returned and the id is incremented.
> > 
> > This could effectively make sqlInsert a little easier.
> > 
> > $core->sqlInsert($data_array, "table_name", TRUE);
> > 
> > The TRUE telling sqlInsert to increment. It would already know WHAT to
> > increment from the sequencer table. So you could even have:
> > 
> > $core->sqlInsert($data_array, "table_name");
> > 
> > With an automatic check to the sequencer table, effectively returning us
> > to the original format... that we had... 90 commits ago... ;-)
> > 
> > Let me know what you guys think...
> > 
> > Matthew McNaney
> > Internet Systems Architect
> > Electronic Student Services
> > Email: ma...@tu...
> > URL: http://phpwebsite.appstate.edu
> > Phone: 828-262-6493
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net emial is sponsored by: Influence the future of 
> > Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
> > program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> > http://www.sun.com/javavote
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of 
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
> program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Don S. <do...@se...>]

I like this better than just selecting the max ID from the table and 
incrementing.

I'm assuming you lock the sequencer table while incrementing?  If so is 
there any chance of creating dead-locks on multiple inserts?

Don.

On Mon, 21 Oct 2002, Matthew McNaney wrote:

> 
> > I would like to tak a closer look at the implemetation of this.  It
> > looks like it's creating an extra table just to calculate the next
> > sequence number.  Do you really want this since it could effectively
> > double the amount of tables in the database?
> 
> Hmmm. There might be a way around this.
> 
> Say we create our OWN sequencer.
> 
> table : core_sequencer
> -----------------
> column : table_name
> column : primary_key_name
> column : current_id
> 
> When sqlImport calls "create table" with a primary key then the table name
> and key are inserted into the sequencer.
> 
> Then when sqlInsert is called the table name is selected. The column name
> and current id are returned and the id is incremented.
> 
> This could effectively make sqlInsert a little easier.
> 
> $core->sqlInsert($data_array, "table_name", TRUE);
> 
> The TRUE telling sqlInsert to increment. It would already know WHAT to
> increment from the sequencer table. So you could even have:
> 
> $core->sqlInsert($data_array, "table_name");
> 
> With an automatic check to the sequencer table, effectively returning us
> to the original format... that we had... 90 commits ago... ;-)
> 
> Let me know what you guys think...
> 
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of 
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
> program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Matthew M. <ma...@tu...>]

> I would like to tak a closer look at the implemetation of this.  It
> looks like it's creating an extra table just to calculate the next
> sequence number.  Do you really want this since it could effectively
> double the amount of tables in the database?

Hmmm. There might be a way around this.

Say we create our OWN sequencer.

table : core_sequencer
-----------------
column : table_name
column : primary_key_name
column : current_id

When sqlImport calls "create table" with a primary key then the table name
and key are inserted into the sequencer.

Then when sqlInsert is called the table name is selected. The column name
and current id are returned and the id is incremented.

This could effectively make sqlInsert a little easier.

$core->sqlInsert($data_array, "table_name", TRUE);

The TRUE telling sqlInsert to increment. It would already know WHAT to
increment from the sequencer table. So you could even have:

$core->sqlInsert($data_array, "table_name");

With an automatic check to the sequencer table, effectively returning us
to the original format... that we had... 90 commits ago... ;-)

Let me know what you guys think...

Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Don S. <do...@se...>]

Yes it does create a table for each seq, and so it would create a table 
for every table that uses sequences.  I don't know if every table uses 
sequences, but to play devil's advocate let's say they do.

As far as database space, the sequence tables are just one int field.  I 
don't think that size would really be a concern.

If your concern is more organizational, I guess there's not much one can 
do to take advantage of the PEAR system.  Personally I don't mind having 
the table created.  I'm sure the PEAR folks took a long, hard look at this 
as well.  They had to make a number of compromises in the name of database 
abstraction, obviously.

I don't think this is that much of a concern.  Of course I'm just a fan.

Don.

On Mon, 21 Oct 2002, Adam Morton wrote:

> I would like to tak a closer look at the implemetation of this.  It looks
> like it's creating an extra table just to calculate the next sequence
> number.  Do you really want this since it could effectively double the
> amount of tables in the database?
> 
> Adam
> 
> > +1 from me on sqlInsert() with idColumn, returnMaxId, and table name as
> > sequence name.
> >
> > Adam
> >
> >> Probably not.  I wasn't aware that PEAR changed the name behind the
> >> scenes.  So just using $table_name in the php code should work great.
> >>
> >> Thanks for the heads-up.
> >>
> >> Don.
> >>
> >> On Mon, 21 Oct 2002, Matthew McNaney wrote:
> >>
> >>>
> >>> > I'm wondering if using the table_name as the sequence name will
> >>> work
> >>> on all db systems.  I don't know explicitly if it won't work, but
> >>> could there  be a possibility of naming collisions?
> >>> >
> >>> > Perhaps using "seq_$table_name" would suit?
> >>>
> >>> I just noticed that PEAR saves the sequence tables as
> >>> sequenceName_seq
> >>>
> >>> So prefixing creates:
> >>>
> >>> seq_sequenceName_seq
> >>>
> >>>
> >>> Do we still want the prefix?
> >>>
> >>> Matt
> >>>
> >>>
> >>>
> >>>
> >>> -------------------------------------------------------
> >>> This sf.net email is sponsored by:ThinkGeek
> >>> Welcome to geek heaven.
> >>> http://thinkgeek.com/sf
> >>> _______________________________________________
> >>> Phpwebsite-developers mailing list
> >>> Php...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >>>
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> This sf.net email is sponsored by:ThinkGeek
> >> Welcome to geek heaven.
> >> http://thinkgeek.com/sf
> >> _______________________________________________
> >> Phpwebsite-developers mailing list
> >> Php...@li...
> >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >
> >
> > ---------------------------------
> > Adam Morton
> > Developer - Web Technology Group
> > Appalachian State University
> > http://phpwebsite.appstate.edu
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 
> 
> ---------------------------------
> Adam Morton
> Developer - Web Technology Group
> Appalachian State University
> http://phpwebsite.appstate.edu
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of 
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
> program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Adam M. <ad...@tu...>]

I would like to tak a closer look at the implemetation of this.  It looks
like it's creating an extra table just to calculate the next sequence
number.  Do you really want this since it could effectively double the
amount of tables in the database?

Adam

> +1 from me on sqlInsert() with idColumn, returnMaxId, and table name as
> sequence name.
>
> Adam
>
>> Probably not.  I wasn't aware that PEAR changed the name behind the
>> scenes.  So just using $table_name in the php code should work great.
>>
>> Thanks for the heads-up.
>>
>> Don.
>>
>> On Mon, 21 Oct 2002, Matthew McNaney wrote:
>>
>>>
>>> > I'm wondering if using the table_name as the sequence name will
>>> work
>>> on all db systems.  I don't know explicitly if it won't work, but
>>> could there  be a possibility of naming collisions?
>>> >
>>> > Perhaps using "seq_$table_name" would suit?
>>>
>>> I just noticed that PEAR saves the sequence tables as
>>> sequenceName_seq
>>>
>>> So prefixing creates:
>>>
>>> seq_sequenceName_seq
>>>
>>>
>>> Do we still want the prefix?
>>>
>>> Matt
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This sf.net email is sponsored by:ThinkGeek
>>> Welcome to geek heaven.
>>> http://thinkgeek.com/sf
>>> _______________________________________________
>>> Phpwebsite-developers mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
> ---------------------------------
> Adam Morton
> Developer - Web Technology Group
> Appalachian State University
> http://phpwebsite.appstate.edu
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Lang Directory Proposal

[Matthew M. <ma...@tu...>]

Good plan +1 here
> I propose that for each module we have a lang directory.  As it works
> now all the language files are put into the setup directory.  Once there
> are many translations then this directory will end be cluttered with
> language and setup files.  I think seperating out the language files
> would make things more organized.
>
> Please Vote!
>
> --
> Steven Levin
> Electronic Student Services
> Appalachian State University
> Phone: 828.262.2431
> PhpWebsite Development Team
> URL: http://phpwebsite.appstate.edu
> Email: st...@NO...
>
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403

Re: [Phpwebsite-developers] Lang Directory Proposal

[Adam M. <ad...@tu...>]

+1 here

> I propose that for each module we have a lang directory.  As it works
> now all the language files are put into the setup directory.  Once there
> are many translations then this directory will end be cluttered with
> language and setup files.  I think seperating out the language files
> would make things more organized.
>
> Please Vote!
>
> --
> Steven Levin
> Electronic Student Services
> Appalachian State University
> Phone: 828.262.2431
> PhpWebsite Development Team
> URL: http://phpwebsite.appstate.edu
> Email: st...@NO...
>
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu

[Phpwebsite-developers] Lang Directory Proposal

[Steven L. <st...@tu...>]

I propose that for each module we have a lang directory.  As it works now
all the language files are put into the setup directory.  Once there are
many translations then this directory will end be cluttered with language
and setup files.  I think seperating out the language files would make
things more organized.

Please Vote!

-- 
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@NO...

Re: [Phpwebsite-developers] NOTICE

[Steven L. <st...@tu...>]

Doh... lol  This is going to blow menuman out of the water.  Hopefully it
will not be too much of a problem to fix :)

+1 though, it is good this stuff is being taken care of now.

> Ok the install will work now. sqlImport creates a sequence table for
> every table created with a primary id field.
>
> As each of you are converting your modules please be aware of some
> things.
>
> Remove the auto_increments from your CREATE statements. Make sure the id
> column is set as a primary key that is unsigned.
>
> Make sure you are not locking your tables before inserting if you want
> to auto_increment. The PEAR sequencer does this automatically and your
> lock will conflict. Use the returnId parameter if you need the last
> column id.
>
> When you install, boost will not translate some statements. I am looking
> in to that.
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> ICQ: 141057403
>
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


-- 
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@NO...

Re: [Phpwebsite-developers] NOTICE

[Don S. <do...@se...>]

Rock.

Don.

On Mon, 21 Oct 2002, Matthew McNaney wrote:

> Ok the install will work now. sqlImport creates a sequence table for every
> table created with a primary id field.
> 
> As each of you are converting your modules please be aware of some things.
> 
> Remove the auto_increments from your CREATE statements. Make sure the id
> column is set as a primary key that is unsigned.
> 
> Make sure you are not locking your tables before inserting if you want to
> auto_increment. The PEAR sequencer does this automatically and your lock
> will conflict. Use the returnId parameter if you need the last column id.
> 
> When you install, boost will not translate some statements. I am looking
> in to that.
> 
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> ICQ: 141057403
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of 
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
> program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
> http://www.sun.com/javavote
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 

Re: [Phpwebsite-developers] NOTICE

[Matthew M. <ma...@tu...>]

Ok the install will work now. sqlImport creates a sequence table for every
table created with a primary id field.

As each of you are converting your modules please be aware of some things.

Remove the auto_increments from your CREATE statements. Make sure the id
column is set as a primary key that is unsigned.

Make sure you are not locking your tables before inserting if you want to
auto_increment. The PEAR sequencer does this automatically and your lock
will conflict. Use the returnId parameter if you need the last column id.

When you install, boost will not translate some statements. I am looking
in to that.

Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403

Re: [Phpwebsite-developers] Translate and templates

[Adam M. <ad...@tu...>]

> $myTemp["text1"] = $_SESSION["translate"]->it("Welcome to my website");
> $myTemp["text2"] = $_SESSION["translate"]->it("Blah Blah");

I think the above method would work for translations in templates.  If all
non-HTML output in a template was in tags then everything could be
translated.  Again it does depend on the module writer to take advantage.

Adam

---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Adam M. <ad...@tu...>]

+1 from me on sqlInsert() with idColumn, returnMaxId, and table name as
sequence name.

Adam

> Probably not.  I wasn't aware that PEAR changed the name behind the
> scenes.  So just using $table_name in the php code should work great.
>
> Thanks for the heads-up.
>
> Don.
>
> On Mon, 21 Oct 2002, Matthew McNaney wrote:
>
>>
>> > I'm wondering if using the table_name as the sequence name will work
>> on all db systems.  I don't know explicitly if it won't work, but
>> could there  be a possibility of naming collisions?
>> >
>> > Perhaps using "seq_$table_name" would suit?
>>
>> I just noticed that PEAR saves the sequence tables as
>> sequenceName_seq
>>
>> So prefixing creates:
>>
>> seq_sequenceName_seq
>>
>>
>> Do we still want the prefix?
>>
>> Matt
>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu

[Phpwebsite-developers] NOTICE

[Matthew M. <ma...@tu...>]

I have updated the core installation files to the new auto increment
format. However, I have hit a snag in the sqlImport function as it blindly
queries the commands it is sent.

So while I work on sqlImport creating a sequence on the CREATE query,
installation will NOT work.

More to come...


Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Don S. <do...@se...>]

Probably not.  I wasn't aware that PEAR changed the name behind the 
scenes.  So just using $table_name in the php code should work great.

Thanks for the heads-up.

Don.

On Mon, 21 Oct 2002, Matthew McNaney wrote:

> 
> > I'm wondering if using the table_name as the sequence name will work on
> > all db systems.  I don't know explicitly if it won't work, but could
> > there  be a possibility of naming collisions?
> >
> > Perhaps using "seq_$table_name" would suit?
> 
> I just noticed that PEAR saves the sequence tables as
> sequenceName_seq
> 
> So prefixing creates:
> 
> seq_sequenceName_seq
> 
> 
> Do we still want the prefix?
> 
> Matt
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Matthew M. <ma...@tu...>]

> I'm wondering if using the table_name as the sequence name will work on
> all db systems.  I don't know explicitly if it won't work, but could
> there  be a possibility of naming collisions?
>
> Perhaps using "seq_$table_name" would suit?

I just noticed that PEAR saves the sequence tables as
sequenceName_seq

So prefixing creates:

seq_sequenceName_seq


Do we still want the prefix?

Matt

Re: [Phpwebsite-developers] Translate and templates

[Steven L. <st...@tu...>]

Well I think in this case they would just have to provide another
translation in the language module.

>> If someone wants it to say
>> something else, they can either go make a translation or just remove
>> the template tag from the template and add their text to the template.
>
> That's what I was thinking but if people are running a multiple language
> site, they may complain that they are stuck with the text hardcoded in
> the template.
>
> I suppose it is up to the module developer.
>
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> ICQ: 141057403
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


-- 
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@NO...

Re: [Phpwebsite-developers] Translate and templates

[Matthew M. <ma...@tu...>]

> If someone wants it to say
> something else, they can either go make a translation or just remove the
> template tag from the template and add their text to the template.

That's what I was thinking but if people are running a multiple language
site, they may complain that they are stuck with the text hardcoded in the
template.

I suppose it is up to the module developer.


Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Matthew M. <ma...@tu...>]

I'll +1 on both the parameter naming and seq prefixing.
Matt


> I'm wondering if using the table_name as the sequence name will work on
> all db systems.  I don't know explicitly if it won't work, but could
> there  be a possibility of naming collisions?
>
> Perhaps using "seq_$table_name" would suit?
>
> Just playing devil's advocate ...

Re: [Phpwebsite-developers] PEAR DB and auto_increment

[Don S. <do...@se...>]

I'm wondering if using the table_name as the sequence name will work on 
all db systems.  I don't know explicitly if it won't work, but could there 
be a possibility of naming collisions?

Perhaps using "seq_$table_name" would suit?

Just playing devil's advocate ...

Don.

On Mon, 21 Oct 2002, Matthew McNaney wrote:

> Here is the CVS link:
> http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/core/Database.php?r=1.25&Horde=cd378aebc4cbdedfdfd10c2df9052480
> 
> 
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>