Hi Charles,

charles girardot wrote:

Hi Kjell,

OK will commit.

Two little things:

1. Where is the place I should make the change in CVS: under include, there is a local and local_distr directory that both contain reporter_columns.inc.php....


local_distr is present in the "source" tree, and gets copied to local in the installation tree. If you install on top of the source, you will see them beside eachother. local_distr is the one we need to update.

2. Kjell, what the version of the pgsql you use? We have problem to load reporter map, all crashes when we do this. Reporter lines are inserted but nothing in the feature table (and other).

version 7.3.9, but we are running an old version of base in production (1.2.10) that haven't gotten the Feature table in place yet. But I haven't run into any problems loading a reporter map on the development machine either, a fresh install of 1.2.17. Is the installation an upgraded one? Maybe there was a problem in the migrate script when the Feature table was introduced or similar ?

K.


Thanks

Charles



On 11 févr. 06, at 20:14, Kjell Petersen wrote:

Hi Charles, all,

Yes, I had to do the exact same change a couple of weeks ago! And I also wondered why I hadn't bumped into the error before when inserting rows. I may have been some code that was updated and now tried to insert using the insert statement itself, instead of defaults stated in the SQL definition of the table.

I think it's an edit that can be safely committed to the CVS.

Cheers,
Kjell

charles girardot wrote:

Hi,

We use BASE with MySQL but we are planning to move to pgsql at some point. So we installed BASE (latest) with pqsql (version 8.1.0). We just tried to load a reporter map and BASE was reporting errors due to invalid SQL about the omim and locuslink columns. It is clearly something that works with MySQL and I can't imagine this to be buggy in PgSQL since this should have been reported already. We traced the error and found that, in the SQL (both mysql and pgsql), these 2 columns are defined as integer while the reporter_columns.inc.php defines them as XCOL_STRING.

We changed XCOL_STRING to XCOL_INT and it worked fine. In fact, I wonder why it works with MySQL and , maybe with older version of PgSQL...

I haven't made the change in CVS yet as I am a bit surprised by the fact it worked so far and because it seems that it was not a problem until here.

Could PgSQL users comment on this? Do you changed this ( XCOL_STRING to XCOL_INT) on your installations?


Cheers

Charles



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel? cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
The BASE general discussion mailing list
basedb-users@lists.sourceforge.net
unsubscribe: send a mail with subject "unsubscribe" to
[EMAIL PROTECTED]




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel? cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
The BASE general discussion mailing list
basedb-users@lists.sourceforge.net
unsubscribe: send a mail with subject "unsubscribe" to
[EMAIL PROTECTED]




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
_______________________________________________
The BASE general discussion mailing list
basedb-users@lists.sourceforge.net
unsubscribe: send a mail with subject "unsubscribe" to
[EMAIL PROTECTED]




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
The BASE general discussion mailing list
basedb-users@lists.sourceforge.net
unsubscribe: send a mail with subject "unsubscribe" to
[EMAIL PROTECTED]

Reply via email to