Did you look at /usr/share/postgresql/$PGVERSION/contrib/rdkit.sql?
This is where it would be on a Debian-based system.

On Tue, Jul 5, 2011 at 14:03, Greg Landrum <[email protected]> wrote:
> Dear Paul,
>
> On Tue, Jul 5, 2011 at 2:55 PM,  <[email protected]> wrote:
>>
>> dear rdkitters,
>>
>> i'm following greg's great emolecules tutorial.
>> psql was installed by our sysadmin on my linux pc. therefore, i'm not 100%
>> familiar with all installation settings.
>>
>> createdb works.
>> but i wonder where to find rdkit.sql?
>> according to the wikie (
>> http://code.google.com/p/rdkit/wiki/DatabaseCreation2), it is placed
>> in /usr/local/pgsql/share/contrib/rdkit.sql.
>> this does not hold true on my pc - i would have been actually surprised...
>
> Do you know if your sysadmins followed the instructions for building
> and installing the cartridge
> (http://code.google.com/p/rdkit/wiki/BuildingTheCartridge)? That
> process creates the rdkit.sql file.
>
> -greg
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Rdkit-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
>

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Rdkit-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss

Reply via email to