Jump to content

jcombs_31

Staff Alumni
  • Posts

    2,064
  • Joined

  • Last visited

Posts posted by jcombs_31

  1. Why then not do something like:

     

    fields

    field_id

    field_name

     

    actions

    action_id

    action_name

     

    fields_actions

    field_id

    action_id

     

    I think this is what I was looking for.  Was having a mental block.  Thanks ignace.  I think though this leads to an additional table.  Table 2 in my scenario also has additional data, for example notes, creation date, etc...

  2. could you post your tables and what are you trying to do exactly?.... a first glance and based only in the small piece of information that you posted the design seems very curious imho

     

    What I'm really doing is creating an enum of sorts.  I just need that enum to be flexible which is why I'm using another table to populate it.  The extraneous data is someone irrelevant.  Ultimately this is a relation between 2 tables.

     

    <table1>

    id

    action

     

    <table2>

    id

    field1

    field2

    field3

    ....

     

    The values for table2 will be driven from the options available in table1.

  3. Ok, I for whatever reason just feel like I'm going about the design wrong, I guess because I never had to build a table like this.  We use an internal system with a number of fields that we need to conduct reviews on.  Each of these will be 'graded' with a follow up action.  I guess this is the only real way to do it, just wanted to be sure.  Thanks for the answer.

  4. I'm thinking maybe I'm going about this wrong, so here it goes.

     

    I have a table, lets call it actions, defined with only a couple fields (id, summary). 

     

    Data would be like:

     

    1 Update

    2 Follow Up

    3 Close

    ....

     

    I have a table with a number or fields that would reference actions.  Ultimately this is for a review of sorts.  I need to have about 10-15 fields reference the available 'actions' as defined in the actions table.  Would I have to define each foreign key separately, or is there a better way to accomplish what I want.

     

    Table 2 has a number for foreign keys.

     

    field 1 => action

    field 2 => action

    field 3 => action

     

    So the constraints look like

     

    foreign key (field1) references actions(id)

    foreign key (field2) references actions(id)

    foreign key (field3) references actions(id)

     

    I thought this could be written as:

     

    foreign key(field1, field2, field2) references actions(id), but apparently I was sadly mistaken.

     

    I've been away from any type of dev for a while, so any thoughts would be appreciated.

  5.  

    In all, IE6 should not be used by the average Jo. We tell all our clients that we are not supporting it, and if they use it they must upgrade.

     

    As Pikachu2000 says, "Shitcan it".

     

    ...and many people would argue the same about you still being on Windows XP...it was released like 9 years ago, and has been since replaced twice over...first with Vista (about 4 years ago) and now by  Windows 7 (been out for over a year now...).

     

    No offense dude...if you wanna continue to use XP then more power to you, but I don't think you really have room to complain about IE9 not being compatible with XP.

     

    Agreed.  Pretty ignorant argument to begin with.  People love to bash MS without praising them for recognizing their mistakes and getting better. 

  6. Cool, thanks guys. I've used trac but never set it up myself.  I don't need anything complex, its really just for small projects but I'm trying to get a little more organized since I have a million things going on.

  7. Well it may be a basic issue, but I cant seem to get around it. In cakephp I am passing args by using routes. Now Say I use hyperlinks like

     

    http://localhost/myapp/t/tag1 

     

    everything works fine. However, what I am trying top accomplish is to make that last bit of the url (tag1) a variable and pass it value from an input box. Now I have the input box and a submit button ready, where I am stuck is how to pass the value of the input box as tag1???? Whatever I do, the controller action receives an empty value (or may be no value). Any help please guys ....

     

    You have to pass the value from your controller to the view for it to be accessible.

  8. When you say drop down are you referring to a select box in a form?  If you submit the form, they will be in the data array.  If you want to pass values to a view, you have to use $this->set('name', $value).  You could just pass the data array and parse as necessary.  And what version of cake are you using, thtml pages are deprecated.

  9. If you have to access outside of the document root there is no reason not to use just 1 install of the cake core files.  You will still need 2 app folders, one for each site, but both config files will point to the cake php core files.

  10. I scalped my forehead about 9 years ago in a car accident, but never took any pictures.  It was pretty nasty and took about a year to really heal up.  Almost had to get a graft.

     

    But yes, i'm glad it is Friday too!

  11. I need to allow users to upload images and resize the images on the client.  Does anyone have a (complete) solution for this? Money is no problem.

     

    Uploading and resizing is done on the server, not the client.  There are probably a million and one free examples and scripts online if you did a simple google search.

  12. I see people complaining all the time about clients doing things like this. These things wouldn't happen (or at least, you wouldn't have to put up with it), if you mention it in the contract to begin with.  Never assume anything goes without saying, no matter big or small, because it doesn't.  It doesn't matter how obvious or common sense or de facto something is.  If it is not clearly stated in your contract what you will and won't do, what can/will/will not happen in the event of xyz, you will put yourself in the position of having to argue with the customer, and since that's something you generally try to avoid, you will more than likely end up catering to it, regardless of how dumb it is. 

     

    People laugh at and curse the client for things like this, and I do to, but I also laugh at the designer/dev for their failure to make a good SOW.  IMO that shows lack of business experience.  I mean how many times you got to go through that song and dance before you say fuck that noise, and start making that SOW TL;DR. 

     

    This is true, but lengthy contracts can also scare aware small business owners.  Once you start discussing the limits of the contract they may just decide to go elsewhere.  Sure, maybe you avoided a pain in the ass client, but you also lost work.  I think you have to walk a thin line with what is in your contract and what your willing to do for a customer.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.