I am not very familiar with the back end code yet but what I can understand
from what you are saying is that the perl files have changed due to changes
in the database side and they need to be tested again. rite?
So, does that mean that I cant test the php front end completely along with
the reservation process till the back end is fixed and updated? If yes, i
wil try to look into that and see how extensive are the changes.
Josh, you said that 2 computers would be sufficient to do the testing part.
So, can that be setup at your end for me to start testing the code.
On Thu, Jun 3, 2010 at 9:06 AM, Aaron Peeler <aaron_pee...@ncsu.edu> wrote:
> On 6/2/10 2:15 PM, Kiran N wrote:
>> Thank you Josh! Let me see if I can work that out.
>> At this point I also had 2 questions.
>> There are some sql statements in the perl scripts running in the back end
>> managment node rite? So in case the back end perl scripts are not
>> that would be using mysql and php would be getting data from derby
>> As an initial phase of testing would this option work for testing front
>> when making a reservation?
> I not sure I completely understand the question/statement. But to clarify,
> yes there are a number of sql statements on the backend perl side. The
> previous work that Milan did for the backend is likely not working anymore
> to support derby, as the schema and the backend datastructure has
> changed/extended since he worked on it. Which highlights the issue of
> continued support for this multiple databases and that we need to backup and
> bit and really design this out on the best way to build in support for
> multiple databases.
> If I mis-read the question/statement, please let me know.
> Secondly, the option Manage images->Edit image grouping and
>> Manage images -> Edit emage mapping
>> These 2 options dont fetch any results/data basically when I try to do
>> groups the page just hangs(mysql db). Also, the UI expands outside the
>> footer of the page. Do I need to get any new php files which has this
>> On Wed, Jun 2, 2010 at 1:49 PM, Josh Thompson<josh_thomp...@ncsu.edu