UCOSP status report #2
Friday, February 5, 2010
For the past 2 weeks, I have been working with the first 2 patches, issimple and isempty, with the first one committed and second one pending for approval. These patches are compiled based on the latest from the GEOS library repository after the people working on it fixed the building issue, and applied the patch sent by my mentor Alex Trofast.
Next moving on, I'm going to work closely with Sara on the SEP testing and hopefully and compile a set of steps for newbies to QA for Ingres.
Wiki pages that I have been reading about.
http://community.ingres.com/wiki/Test_Developer
http://community.ingres.com/wiki/SEPGUIDE
Posted byA nerdy girl at 9:37 AM 0 comments
Labels: Eva Wong, Geospatial, Ingres, status report, UCOSP, winter 2010, Wong I Wa
UCOSP status report #1
Friday, January 22, 2010
For the first week, I have tried stepped through the code in Ingres using the build that is generated by ./runbuild.sh -g after a clean along with gcc.
For the first patch isempty, I have the diff patch that I have so far to Andrew, Alex, and Sara. I have got a confirmation from Alex that the patch Right now I'm currently stuck on some build error that is at this point unknown to me.
I have followed the exact same steps for this way of clean build.
In $ING_ROOT:
rm -rf release install build logs tools
./runbuild.sh -c
cd src
rm -rf `svn stat | grep ? | awk '{ print $2'`
runbuild.sh -g
However, the build gave me the following error
grep --color -n error ./logs/jam_01_23_10_0309.log
1384:/data/g7iwwong/geospatial/src/common/adf/adg/adgoptab.c:1106: error: 'ADO_ISEMPTY_CNT' undeclared here (not in a function)
1385:/data/g7iwwong/geospatial/src/common/adf/adg/adgoptab.c:1106: error: 'ADZ_ISEMPTY_FIIDX' undeclared here (not in a function)
Posted byA nerdy girl at 12:47 PM 0 comments
Labels: Eva Wong, Geospatial, Ingres, status report, UCOSP, winter 2010, Wong I Wa
UCOSP: status report #14
Tuesday, November 24, 2009
Back on Wednesday, I have committed the "guiding patch" into the repository. I followed these steps, confirmed with the Ingres community that this is how I should be working for development:
- Go to https://bugs.ingres.com/ to create a ticket as "New enhancement" for development. The ticket system is not only used for bugs, but also development purpose.
- do "svn commit --username=yourUserName /path/to/file.s -m=#123456 your description", where 123456 is the ticket number that you have created
- commit 1 fix/small feature at a time
- after committing, send off a quick email notifying everyone that something has just committed.
Other than that, I have also been reading on this knowing more about the structure of the Ingres code.
As for my understanding now, the current development is currently focusing on improving the robustness of this following part.
adu – This is where most of the actual expression and function semantics live. ADU contains code for string functions, date functions, coercions, and more.
For the rest of the week, I'll be working closely with Chuck Thibert on the small part that he's also working on.
Posted byA nerdy girl at 6:26 PM 0 comments
Labels: Eva Wong, Geospatial, Ingres, status report, UCOSP
UCOSP: status report #12
Friday, November 13, 2009
I have talked with the system administrator, Greg, Andrew, IRC to get me enough quota for the C code to build the code.
I am right now working on the install of the components and build the Ingres code hopefully within this weekend.
Posted byA nerdy girl at 7:03 AM 0 comments
Labels: Ingres, status report, UCOSP
Fix: Errno 3502, no GRANT or GRANT compatible permit exists
Tuesday, November 3, 2009
aka, UCOSP: status report #12
Here is a piece of php code that I ran to check I can execute query under my web server.
There it prints this error message:
no GRANT or GRANT compatible permit exists
Reason:
By default, when you create a database, the access to the database is public.
By default, when you create a table/view/procedure the access is restricted to the owner.
You will need to do "grant select on the_table/view/procedure_you_want to public". For convenience, I did "grant all on test" and ran the code above. Remember you will NEED TO log off the database where that table is sitting in order for the above code to work :)
Posted byA nerdy girl at 10:32 AM 0 comments
Labels: 3502, no GRANT or GRANT compatible permit exists, status report, UCOSP
Code: Test if Apache is working with Ingres
Friday, October 30, 2009
The following is a piece of code that will help to see if Apache is talking to Ingres
error_reporting(E_ALL);
$link = ingres_connect("your_whatever_database_name")
or die("Could not connect");
echo "Connected successfully
";
?>
Ingres by default creates database with the access type public. If you explicitly put in a user name or password as parameters to ingres_connect for public database, it will fails to connect.
Now that I know Apache is talking to Ingres, next Drupal!
Posted byA nerdy girl at 10:53 PM 0 comments
Labels: apache, Ingres, status report, test, UCOSP
UCOSP: status report #8
Monday, October 26, 2009
I'm trying to get Drupal 7 to talk to Ingres 10 following this here on Windows 32 bit XP home SP3, with PHP 5.3 and Apache 2.2. When I run the script from http://localhost:8080/drupal-6.14/install.php, and it's stucked on
Database configuration
Your web server does not appear to support any common database types.
I have these 2 lines in my php.ini under Apache
extension_dir=C:\php\ext
extenion=php_ingres.dll
The funny thing is Drupal knows about other extension such as php_mysql.dll, but the php_ingres.dll does not, which are also located in C:\php\ext like php_mysql.dll. I have got my version of php_ingres.dll from Grant earlier today since the dll is not up on ESD for Ingres version 10 yet(Thanks so much for Grant again on this).
Apparently, I'm not the only one of the UCOSP students who are still stucked on this. Sarah and Mary has got away from this problem by installing a Linux VM and Evan is still working on it. ARGH, I really want to get this working soon!
Posted byA nerdy girl at 9:31 PM 0 comments
Labels: status report, UCOSP
UCOSP: status report #5
Saturday, October 24, 2009
At the meeting today, Evan, Sarah, and I, the three of us discussed the pitfalls of using xampp to make drupal to talk directly with Ingres. They helped me to discoverred that my configuration was not right and my drupal was based on mysql but not Ingres.
Besides, preparing ourselves to build the code, we were comparing our understanding of what exactly is Geospatial. Since we are all not sure if Geospatial is a "specialist" of Ingres or a plugin to Ingres. I can see that we are building the Geospatial code which is one of the branches under Ingres in the repository, and the structure is almost identical to the main Ingres code base, which suggests that it may be the former.
Next week goal: Fix the communication between Drupal and Ingres.
Posted byA nerdy girl at 4:06 PM 0 comments
Labels: status report, UCOSP
UCOSP: status report #3
Friday, October 16, 2009
For this week, I have been getting myself working around with subversion of Microsoft Visual Studio. Ankhsvn is the one that I have got. For next week, since it is packed with midterms, I will keep on working with subversion until next Friday before I'll be resuming my work.
Posted byA nerdy girl at 9:57 PM 0 comments
Labels: status report, UCOSP
UCOSP status report #2
Friday, October 9, 2009
I have been spending this week to get myself familiar with Microsoft Visual Studio and its .NET components. Such as using debugger, watching tutorial videos and demos of how to use the tool to write C code. Next week goal: Build Ingres.
Posted byA nerdy girl at 9:13 PM 0 comments
Labels: status report, UCOSP
UCOSP status report #1
Friday, October 2, 2009
A week after the code sprint, the configurations is still going on. This week I have configured Drupal with the remaining modules left over from code sprint, as well as Ingres. Also I have obtained a copy of Microsoft Visual Studio 2005 and its .NET components for moving on to building of Ingres. Since I'm new to Visual Studio and the .NET framework, I will be spending next week to get myself familiar with Microsoft Visual Studio and its .NET components. If I have time, then I'll move onto the building of Ingres.
Posted byA nerdy girl at 9:05 AM 0 comments
Labels: status report, UCOSP