Tore

Hi. I would like to be able to find weeknumber and weekdaynumber without using the UNIX timestamp (e.g use of mktime). I'm looking for a function that use a date to calculate the above. The reason I'm asking is that I would like to display calendars further back in time that the UNIX timestamp handles. Does anyone out there know if there is a custom function somewhere that are able to calculate which weeknumber a given date is within? would also appreciate something that also find the weekdaynumber for a given date, preferably for both using monday and sunday as the first day of the week?

Hi. I have one Login form that collects UserID and Password. I will hide UserID and Password from network sniffers and encrypt the traffic between client and server using OpenSSL. After the user has logged in I want the user to continue using other scripts in one particular directory without using SSL. I\'m assuming that since I keep track of the user using a generated SessionID (using PHP) when he logged in, I can keep sniffers away. Is this right or can a \'sniffer\' actually grab my members SessionID and use it for getting access to my members pages? I would like to run only one apache webserver! Same webserver for clients just browsing without logging in (not using SSL), and for my members when they log in (use SSL just for login in). How to I do this? And how should the directory structure be like for making it work?

Hi. I have a site called let say: www.mydomain.com My members shall access their site using an URL like this: www.mydomain.com/memberx Where memberx is any valid combination of characters, numbers and hyphens. My members pages will actually be on another disk than the document root.... It could be like this: /hde/mem/memberx So I guess I have to use Alias to manage this... Other members could have their pages on another disk like this: /hde/mem/membery Directory listing should not be possible. QUESTION 1: How do I configure httpd.conf file for this particular memberx so it will work as I described above? QUESTION 2: When my member eventually want a .com or .net or whatever URL as well as using the www.mydomain.com/memberx URL, what do I have to add to the httpd.conf file to make it work like that? That is: This particular member want to be able to access his site in two ways: 1. using www.mydomain.com/memberx URL and 2. using i.e. www.somename.com URL. QUESTION 3: How do I prevent other from hotlinking to images on all of my members sites and including my root domain www.mydomain.com?

Hmmm... Do not know what to say. I appreciate your answer, but now I have two different answers to my question. I have posted the same question on three different sites. On one other site a guy say that I should go for the FULLTEXT solution. I to thought it would be faster to store it the way you preferred and not use the FULLTEX solution. But what I think and how it works in real life situation may be different. I might have to send the question to MySql AB ? Anyway thanks again.

Could you please say why you would do it that way, and why you prefer to not use a field that hold all the words and then use a fulltext index on that field. Is this solution faster when finding related tables? Or is there som other reason why you prefer this solution?

See original question!!!

Hi. Have one table with FIXED row length. Table name: \"thetable\". Field 1: MemID (mediumint). (relates to another table members) Field 2: TheID (smallint). Primary key: MemID, TheID. Lots of fields. Fixed table length. I want to make it possible for users to search for records in this table related to one or more keywords. Since I want thetable to be as small as possible I want to store the releated keywords in another table: Solution A: Either in a table called thekey with these fields, keys and indexes: Field 1: MemID. Field 2: TheID. Field 3: Keywords (Varchar (255)). Primary key: MemID, TheID. Index on Keywords field as FULLTEXT index. Solution B: Or in a table called thekey with these fields, keys and indexes: Field 1: MemID. Field 2: TheID. Field 3: Keyword (varchar (30)). Primary key: MemID, TheID, Keyword. Index on Keyword. QUESTION 1: Which of the two solutions will make the fastest select queries if I search like this: Solution A: Searches would be done like this: select TheID from thekey where match (Keywords) against (\'theword\'); Solution B: Searches would be done like this: select TheID from thekey where Keyword like \'theword%\'; or select TheID from thekey where Keyword like \'theword\'; Consider houndreds of thousands of records in table \"thetable\". QUESTION 2: Which of the two solutions will use less diskspace?