n00854180t
10-13-2003, 11:54 AM
I just bought this book yesterday, mostly as a reference. I noticed that in the Foreword PHPB is mentioned :P! Anyway, looks like a pretty good book, nice and comprehensive. Has anyone used this book?
Click to See Complete Forum and Search --> : Core PHP Programming 3rd Ed.
stolzyboy
10-13-2003, 11:58 AM
Originally posted by n00854180t
I noticed that in the Foreword PHPB is mentioned :P!
That's cuz we're the best...
Oh yeah, and cuz we're the best! :D
I noticed that in the Foreword PHPB is mentioned :P!
That's cuz we're the best...
Oh yeah, and cuz we're the best! :D
n00854180t
10-13-2003, 12:38 PM
LOL
stolzyboy
10-13-2003, 12:40 PM
Originally posted by n00854180t
LOL
I think at one time, someone did an article about that book, but not sure, or at least someone was asked to do an article about that book...
LOL
I think at one time, someone did an article about that book, but not sure, or at least someone was asked to do an article about that book...
n00854180t
10-13-2003, 01:25 PM
Really?
Do you do any regular software dev Stolzy? C++ and the like?
Do you do any regular software dev Stolzy? C++ and the like?
stolzyboy
10-13-2003, 01:31 PM
I did awhile back (2+ years), but the closest lately to low level programs is JAVA... I'm too busy with web related work at work to play with anything else...
n00854180t
10-13-2003, 01:41 PM
After I finish my current project for work I am going to have to do some Win32 dev. I haven't really done that much Windows programming, I stuck mostly to small command line stuff and made text games :P If I can ever get a design document together I want to finally put together the Ogre Battle clone (esque) I have been wanting to for so long. I think doing the Win stuff should get me into the thick of it enough to start doing some of that stuff.
On a side note, do you know a good database system for Win32? The current database is in FoxPro and I don't want to deal with it. I already know MySQL and PgSQL, I don't want to have to learn a crappy MS database system (it's version 3.0 too :( ). I don't know if PgSQL would be able to handle the volume of the data in our current db.
On a side note, do you know a good database system for Win32? The current database is in FoxPro and I don't want to deal with it. I already know MySQL and PgSQL, I don't want to have to learn a crappy MS database system (it's version 3.0 too :( ). I don't know if PgSQL would be able to handle the volume of the data in our current db.
stolzyboy
10-13-2003, 01:42 PM
What amounts of data are you looking at?
And what platform will this be, 2K, 2K SERVER, etc...?
And what platform will this be, 2K, 2K SERVER, etc...?
n00854180t
10-13-2003, 01:48 PM
Well it appears to be running on 98SE right now (OMFG that just kills me). If I had my way I would scrap the whole config and put it on Linux.
We have Win2k somewhere around here, although I am not sure if I want to use it. What is a good Win server (relatively speaking that is)? We can just buy the new version when the time comes.
We have Win2k somewhere around here, although I am not sure if I want to use it. What is a good Win server (relatively speaking that is)? We can just buy the new version when the time comes.
stolzyboy
10-13-2003, 01:50 PM
Windows 2000 Server is what we usually use, costs thousands though... The only reason I say to use that is cuz then you can run the MSSQL server... probably the best M$ db...
Other than that, not sure how stable postgre is on windows, but it and MySQL can handle loads of records... and certainly can handle anything that foxpro is running right now.
Other than that, not sure how stable postgre is on windows, but it and MySQL can handle loads of records... and certainly can handle anything that foxpro is running right now.
n00854180t
10-13-2003, 01:54 PM
PgSQL is virtually non-existant on Windows. You have to install CygWin and install a c compiler to run the makefile etc. I got about 1/4 of the way and quit because it was cluttering the root of my drive up.
I think I could probably just go with MySQL but I have seen it used in Windows software, it just doesn't seem to perform that well. We have about 50000 customers in the database and about 40 products ( * lot numbers * variations for different countries etc). I am sure MySQL could handle it, but I don't know how well the software would perform trying to communicate with it.
I think I could probably just go with MySQL but I have seen it used in Windows software, it just doesn't seem to perform that well. We have about 50000 customers in the database and about 40 products ( * lot numbers * variations for different countries etc). I am sure MySQL could handle it, but I don't know how well the software would perform trying to communicate with it.
jstarkey
10-13-2003, 01:56 PM
Originally posted by n00854180t
I don't know if PgSQL would be able to handle the volume of the data in our current db.
I've used postgres on 13 million records and it did fine. It wasn't high traffic, but it was high load (creating topo maps on the fly using PHP/GD).
I don't know if PgSQL would be able to handle the volume of the data in our current db.
I've used postgres on 13 million records and it did fine. It wasn't high traffic, but it was high load (creating topo maps on the fly using PHP/GD).
n00854180t
10-13-2003, 01:58 PM
I would like to have a server OS (such as 2k server) but it is a relatively small business so spending 1000+ on the OS is not very good. I might be able to just stick it on Linux though (although it would be a headache for everyone but me LOL, as everyone in the company are Win users exclusively).
jstarkey
10-13-2003, 02:00 PM
Originally posted by n00854180t
We have about 50000 customers in the database and about 40 products ( * lot numbers * variations for different countries etc).
50,000 records is pretty trivial for any decent DB.
You know, another option may be setting up a $500 machine for just a DB server, installing Linux and PgSQL for free.
We have about 50000 customers in the database and about 40 products ( * lot numbers * variations for different countries etc).
50,000 records is pretty trivial for any decent DB.
You know, another option may be setting up a $500 machine for just a DB server, installing Linux and PgSQL for free.
stolzyboy
10-13-2003, 02:00 PM
Originally posted by n00854180t
(although it would be a headache for everyone but me LOL, as everyone in the company are Win users exclusively).
well, then you'll just have to learn 'em the ways of OUR world
(although it would be a headache for everyone but me LOL, as everyone in the company are Win users exclusively).
well, then you'll just have to learn 'em the ways of OUR world
n00854180t
10-13-2003, 02:01 PM
Originally posted by jstarkey
I've used postgres on 13 million records and it did fine. It wasn't high traffic, but it was high load (creating topo maps on the fly using PHP/GD).
That would be well enough, I think we have enough parts in the graveyard for another server (hehe the graveyard). I could probably slap together a server and put Linux on it, then just make the Win32 software and connect to the server. The only problem is how to migrate a crappy FoxPro db to PgSQL.
I've used postgres on 13 million records and it did fine. It wasn't high traffic, but it was high load (creating topo maps on the fly using PHP/GD).
That would be well enough, I think we have enough parts in the graveyard for another server (hehe the graveyard). I could probably slap together a server and put Linux on it, then just make the Win32 software and connect to the server. The only problem is how to migrate a crappy FoxPro db to PgSQL.
n00854180t
10-13-2003, 02:03 PM
Originally posted by stolzyboy
well, then you'll just have to learn 'em the ways of OUR world
Hehe easier said than done really. Some of the people in the company think win98 is better than XP (Because it is too hard to setup no less LOL).
well, then you'll just have to learn 'em the ways of OUR world
Hehe easier said than done really. Some of the people in the company think win98 is better than XP (Because it is too hard to setup no less LOL).
stolzyboy
10-13-2003, 02:06 PM
Originally posted by n00854180t
The only problem is how to migrate a crappy FoxPro db to PgSQL.
give this (http://server.bo-bo.si/php/dbfConverter/) a whirl, i've gotten it to work with mysql and it says it has PG support, so ya never know...
The only problem is how to migrate a crappy FoxPro db to PgSQL.
give this (http://server.bo-bo.si/php/dbfConverter/) a whirl, i've gotten it to work with mysql and it says it has PG support, so ya never know...
jstarkey
10-13-2003, 02:09 PM
Originally posted by n00854180t
That would be well enough, I think we have enough parts in the graveyard for another server (hehe the graveyard).
Be sure that you don't skimp on the memory. The key is to not let the tables page to disk.
That would be well enough, I think we have enough parts in the graveyard for another server (hehe the graveyard).
Be sure that you don't skimp on the memory. The key is to not let the tables page to disk.
n00854180t
10-13-2003, 02:10 PM
Hehe thanks for the link. I think the conversion process will probably be more of a headache than writing the software.
stolzyboy
10-13-2003, 02:12 PM
Originally posted by n00854180t
I think the conversion process will probably be more of a headache than writing the software.
Not if the link i gave you works as flawlessly with PG as with MySQL.
I converted 23 db's in under an hour once the initial setup was accomplished. That took about 2 hours to get it working the way I wanted it to.
I think the conversion process will probably be more of a headache than writing the software.
Not if the link i gave you works as flawlessly with PG as with MySQL.
I converted 23 db's in under an hour once the initial setup was accomplished. That took about 2 hours to get it working the way I wanted it to.
n00854180t
10-13-2003, 02:13 PM
Originally posted by jstarkey
Be sure that you don't skimp on the memory. The key is to not let the tables page to disk.
Will have to buy Mobo and Mem and such. We mostly just have cases/monitors/cd and floppy drives/couple of hdds/keyboards etc back there. Will have to buy a proc too. What kind ram do you recommend (DDR most likely). Would 1gb be enough? Usually we have about 7 people accessing the db at any one time.
Be sure that you don't skimp on the memory. The key is to not let the tables page to disk.
Will have to buy Mobo and Mem and such. We mostly just have cases/monitors/cd and floppy drives/couple of hdds/keyboards etc back there. Will have to buy a proc too. What kind ram do you recommend (DDR most likely). Would 1gb be enough? Usually we have about 7 people accessing the db at any one time.
n00854180t
10-13-2003, 02:14 PM
Originally posted by stolzyboy
Not if the link i gave you works as flawlessly with PG as with MySQL.
I converted 23 db's in under an hour once the initial setup was accomplished. That took about 2 hours to get it working the way I wanted it to.
Really? Wow. That is damned good. I guess the headaches will be from trying to show people how to use the new db ;P
Not if the link i gave you works as flawlessly with PG as with MySQL.
I converted 23 db's in under an hour once the initial setup was accomplished. That took about 2 hours to get it working the way I wanted it to.
Really? Wow. That is damned good. I guess the headaches will be from trying to show people how to use the new db ;P
jstarkey
10-13-2003, 02:24 PM
Originally posted by n00854180t
Would 1gb be enough? Usually we have about 7 people accessing the db at any one time.
1 gig should take care of it no problem. Especially if it's a dedicated machine and you don't have huge blobs. There's a way to find out if it's paging in postgres, but I can't remember how at the moment. I have only one ongoing project at the moment that's pgsql and it's pretty small -- roughly 30,000 records over 10 tables, so I haven't had to do any optimization other than the normal indexing and vacuuming.
Would 1gb be enough? Usually we have about 7 people accessing the db at any one time.
1 gig should take care of it no problem. Especially if it's a dedicated machine and you don't have huge blobs. There's a way to find out if it's paging in postgres, but I can't remember how at the moment. I have only one ongoing project at the moment that's pgsql and it's pretty small -- roughly 30,000 records over 10 tables, so I haven't had to do any optimization other than the normal indexing and vacuuming.
n00854180t
10-13-2003, 02:29 PM
What is a good proc for something like this? I am not sure really. Looks like pricewatch has a 2.4ghz 400mhz fsb celeron for $79.
jstarkey
10-13-2003, 02:34 PM
Yah, I can't help you there. I use AMD for everything.
n00854180t
10-13-2003, 02:40 PM
Well I would go AMD, but I don't really like the price for the speed. I just checked, it looks like the main differences between the Celeron and the P4 are the l2 (128kb vs 512kb (might have a 256 version of celeron now)) cache and the process (p4 = .13 micron and celeron is .18).
elToro
10-14-2003, 05:32 PM
I would like to have a server OS (such as 2k server) but it is a relatively small business so spending 1000+ on the OS is not very good.
You might look into Microsoft Small Business Server (http://www.microsoft.com/sbserver/).
You might look into Microsoft Small Business Server (http://www.microsoft.com/sbserver/).
PHP Builder
Copyright WebMediaBrands Inc. All Rights Reserved.
Copyright WebMediaBrands Inc. All Rights Reserved.