[eluser]Unknown[/eluser]
Hi,

[eluser][email protected][/eluser]
Hey guys,

I am using the db->simple_query('call procedure();');

and was wondering if this call is asynchronous?

If not, how can I make an asynchronous db call? The procedure takes a while and i don't want the web user waiting that long

???any other ideas???

thanks.

[eluser]dedavai[/eluser]
I'm having trouble accessing variables created inside the controller from within the viewer. For example, inside the controller (home.php) I have the following:

[eluser]schnoodles[/eluser]
Hello i was playing around with active record, and just got stuck with a select statement of

[eluser]sikkle[/eluser]
Hi to this community again

i just want to advise, this is maybe a stupid one but let's go.

We all know, a lot of our work consist to manage the input data, show form, error, validation etc. etc.

so i'm trying to figure what is barely the best practice if i give you this example :

You get a controller, we will call it MyLovelyController.php.

indeed we get the same structure as usual, constructor, index.

imagine this controller is just to do this :

show a form to be fill out by the user, let imagine like old good example, this describe a car.

So

field :

Model (select comin from db model indeed)
Color
Motorhp


So we have to show the form, do the validation, re-show the form with current data until the validation as been accepted And after show a little success bouton to do any action, maybe continu, maybe getback now whatever.


So we get back to our controller :

what is the best practice order, i mean


if data in form, do the validation ?


if validation fail
show error
reload view ?

Else

show the blank form ?

else again

show the success form ?



I know it's not the way to go, but this is a example of what i'm looking for.

someone could be kind enough to give a good explaination of barely best practice with form,validation,error,success,action order ?

Many thanks for this again

[eluser]Référencement Google[/eluser]
Hi,

Using the db_session library to store some session data at almost each page view for each users, I am worry about performances when the website will go live and will have 1000 visitors / hour.

Is it possible that the use of native PHP sessions could be better than using DB to store things like the actual page wich is viewing the visitor in real time (the reason for that is to get him back to the point he was viewing before a redirection for exemple).

What do you think ?

[eluser]Référencement Google[/eluser]
Hi,

I am not sure about how do CI handles native PHP sessions ($_SESSIONS) because I get problems, it seems that my sessions are not kept between pages.

I have a library to manage sessions from DB (db_session) but I would like also to use some sessions as the classic way, having for some things the use of the DB, and for some other things the use of native sessions.

Some code maybe will help:

config.php

[eluser]tmcw[/eluser]
Okay, so working on le CMS... in my public controllers, for each page generated, I've been putting a bit of logic for fetching items from a Page_model, sorting those into a tree, and putting that on a page. I've got it to the point that I at least have that logic in a function within each controller, so I can call it like $data['menu'] = $this->menu('Page_model') and so on.

My question is whether there's a better way to do this... as a helper, plugin, etc? I've been running into the problem that helpers seem to exist outside of the CI object system, so I can't call in a model. Plugins, I think, can, but the manual tells me that they usually have only one associated function. I don't know why.

Any suggestions? It isn't a killer problem, but I figure it's fairly common and I'd like to build this thing the best way I can.

Thanks

[eluser]ryantxr[/eluser]
I use a separate LINUX server to run Apache/PHP/Mysql. I decided to install Apache+PHP on my workstation for quicker experimentation. Code Igniter displays blank pages. Here is what I know so far.

OS: Windows XP
apache 2.2.4
PHP 5.2.3

I verified that PHP is functioning.

I traced through the Code Igniter code and it gets all the way to CodeIgniter.php where it is trying to instantiate the class. From there, it seems to just go nowhere. The following shows where it got to.

[eluser]CI Lee[/eluser]
Hello all...


I had been using pr1.domain.com to preview a site for the client. Now I use domain.com yet the google index still points to pr1.domain.com, when someone clicks that link it is valid because the subdomain (or any for that matter) points to domain.com.

Any suggestions on how to fix that? I have the webmaster tools and can do the url removal if I want however I dont want to lose those inbound links.

-Lee