Git Product home page Git Product logo

glorp's Introduction

GLORP

Pharo Glorp

Unit Tests PostgreSQL Integration Tests SQLite3 Integration Tests Coverage Status

Pharo 8.0 Pharo 9.0 Pharo 10 Pharo 11

Generic Lightweight Object Relational Persistence (for Pharo)

Glorp is a full-featured Object-Relational Mapper which offers a number of features to reduce the 'impedance' between working with objects and storing them in flat tables. Amongst those features, you'll find some features saving you from writing SQL queries by hand, managing transactions that rollback the changes to the objects in your image or commit them to the database, writing simple and complex queries using plain Pharo syntax, and other features that we will cover in this introduction chapter and in the advanced topics chapter.

This port of Glorp is based on VisualWorks Glorp version 8.0.1.

Further information on loading and using Glorp is available in "Object-Relational Persistence with Glorp", available from http://books.pharo.org/

To load Glorp itself:

Metacello new
	repository: 'github://pharo-rdbms/glorp';
	baseline: 'Glorp';
	load.

Note that Glorp requires database drivers for the actual database connectivity:

  • For SQLite3, see Pharo-SQLite3. Use its Metacello snippet to load both Glorp and the driver in one go.
  • For PostgreSQL, see P3. As per its README, load the driver after loading Glorp itself.
  • On Windows, for Oracle and SQLServer, see PharoADO. By default its Metacello snippet loads Glorp and the driver.

ActiveRecord extensions

A recent update adds compatibility with Rails style ActiveRecord database schemas. The Rails folks realized that if a database schema follows some simple conventions, then mapping to objects becomes much easier. The complete ActiveRecord naming convention is detailed at https://guides.rubyonrails.org/active_record_basics.html The following was mostly taken from there.

Tables and Classes

ActiveRecord will pluralize your class names to find the respective database table. So, for a class Book, you should have a database table called books. The ActiveRecord pluralization mechanisms are very powerful, being capable of pluralizing (and singularizing) both regular and irregular words. When using class names composed of two or more words, the model class name should follow the Ruby conventions, using the CamelCase form, while the table name must contain the words separated by underscores. Examples:

  • Model Class - Singular with the first letter of each word capitalized (e.g., BookClub).
  • Database Table - Plural with underscores separating words (e.g., book_clubs).
Model / Class Table / Schema
Article articles
LineItem line_items
Deer deer
Mouse mice
Person people

Table pluralization can be disabled by setting pluralizeTables on the descriptor system.

Schema Conventions

Active Record uses naming conventions for the columns in database tables, depending on the purpose of these columns.

  • Foreign keys - These fields should be named following the pattern singularized_table_name_id (e.g., item_id, order_id). These are the fields that Active Record will look for when you create associations between your models.
  • Primary keys - By default, Active Record will use an integer column named id as the table's primary key (bigint for PostgreSQL and MySQL, integer for SQLite). Primary keys defined as strings will be generated with GUIDs.

There are also some optional column names that will add additional features to Active Record instances:

created_at - Automatically gets set to the current date and time when the record is first created.

updated_at - Automatically gets set to the current date and time whenever the record is created or updated.

deleted_at - When present, delete methods will just update this field to the current timestamp and ActiveRecordQuery will ignore records where deleted_at is not null.

type - Specifies that the model uses Single Table Inheritance.

order - Specifies the order of records when in a to-many relationship. In the event of a link table, the order field is on the link table. A number of synonyms are used to infer ordering fields. By default fields named position sequence_no seq_no sequence_num seq_num sort_no display_position display_order order sort_value sort_key sort are inferred to be sort keys. This can be changed in the ActiveRecordDescriptorSystem.

The ActiveRecord mappings are new and may contain bugs. There are some tests but more are needed. Submission of tests, bug reports, or fixes are welcome.

ActiveRecord support was added by Todd Blanchard

glorp's People

Contributors

akgrant avatar akgrant43 avatar astares avatar emaringolo avatar estebanlm avatar gcotelli avatar guillep avatar ironirc avatar jvanecek avatar lolgzs avatar lopezca avatar mahugnon avatar pharo-todd avatar pierceng avatar serpi90 avatar tblanchard avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

glorp's Issues

CompoundSelectCommand does not generate LIMIT or OFFSET commands in query

When producing SQL from a CompoundQuery object (created by calling unionAll: on 2 queries) , it uses a CompoundSelectCommand object to wrap a SELECT DISTINCT query to the union.

The CompoundQuery object has the limit: and offset: messages, but they do not store any values and simply state:

We currently ignore limit sets and use the one from our contained queries.

Moreover, the CompoundSelectCommand does account for these values and does not generate any SQL even if they are not nil (which is the check SimpleQuery uses).

There are 2 problems with the current implementation:

  1. CompoundQuery should have its own limit and offset variables since the internal queries may have something different for their own reasons (for example count: queries set limit=1 by default).

  2. CompoundSelectCommand should print LIMIT and OFFSET if the CompoundQuery object has values.

I propose the following changes:

  1. Add instance variables (limit, offset) to CompoundQuery to store it's own values, independently of the first union query.

  2. Have CompoundSelectCommand add the wrapper SELECT statement if we have limit or offset values.

ObjectBuilder should raise exception when the descriptor primary key dosen't match the incoming query result stream

When the Glorp ObjectBuilder find that the descriptor primary key provided by the user doesn't match with the incoming query result stream primary key, it returns an empty array even if the SQL query result stream is not empty. This can be easily verified by sending manually the query. I think this can be contrary and problematic because the user doesn't know that there's is a mistake in his mapping at the end and so for him, the database is empty which is not true. This can take a quite amount of time to realize what is going on. To avoid that I suggest that the ObjectBuilder raise an exception or a warning, in this case, to make the user aware of the issue in his mapping.

DatabasePlatform>>#convertToNumber:for: contains a bug

I think DatabasePlatform>>#convertToNumber:for: contains a bug,
Dialect doesPrecisionOf: aNumber equal: aType precision should be:
Dialect doesPrecisionOf: aNumber equal: aType scale.
If you take a look at Dialect class>>#doesPrecisionOf:equal: you can see that terminology has been mixed up (if I'm interpreting it right)

    ^aNumber class == self fixedPointClass and: [aNumber scale = aPrecision]```
method and argument name suggests that precision is being checked, but actually it's the scale that's being compared.

Cleanup: Unnecessary #new overrides

Some classes in GLORP override the #new method like

new

	^ super new initialize

for instance

  • Cache class>>#new
  • CacheManager class>>#new
  • DatabaseAccessor class>>#new
  • GlorpSession class>>#new
  • Login class>>#new
  • PersistentObject class>>#new
  • DatabaseCommand class>>#new
  • TimedProxyReaper class>>#new
  • DatabaseTable class>>#new
  • GlorpPreparedStatement class>>#new
  • GlorpExpression class>>#new
  • Descriptor class>>#new
  • DescriptorSystem class>>#new
  • GlorpAttributeModel class>>#new
  • GlorpClassModel class>>#new
  • Mapping class>>#new
  • AbstractProxy class>>#new
  • ElementBuilder class>>#new
  • Query class>>#new
  • GlorpDatabaseType class>>#new
  • FieldValueWrapper class>>#new
  • RowMap class>>#new

This is not necessary in Pharo as this is already out of the box behavior that a new instance is initialized.

We can get rid of these methods

SQLite3: Tests showing errors

using SQLite3 Glorp-integration-tests shows 1 failure and 483 errors

Environment and SQLite3 were setup as follows
P10 image + Pharo-SQLite3 + glorp + Pharo-SQLite3(SQLite3-Glorp, SQLite3-Glorp-Tests)

GlorpDatabaseLoginResource class>>defaultLogin
	DefaultLogin isNil ifTrue: [^DefaultLogin := self defaultSQLiteLocalLogin].

PharoDatabaseAccessor>>connectionClassForLogin: aLogin 
...
        aLogin database class == SQLite3Platform
             ifTrue: [ ^ Smalltalk at: #SQLite3Driver ].

One2One relations raises duplicated exception if not transitively registered

Let's assume the following one2one relation: A.fk1->B.id.

Glorp handles this case fine when persisting A, if B is not previously registered. Glorp just stores B transitively.

But if B was registered previously with the same session, the storage of A will raise a DuplicatePrimaryKeyException because is trying to register B again.
If you use a pool of sessions, the same story will raise a GlorpDatabaseWriteError instead, with an error raised by the db moto, indicating the intention of storing the duplicated object (when using a single session, glorp finds B in the cache and raises the exception, but with a pool of sessions, the fresh one doesn't have it in its cache, but violates the db constraint).

Would be great that Glorp could check if B.id is nil, in which case should insert the object transitively, but if not just ignore this insertion.

Set up CI

Given the independently evolving drivers for SQLite3, PostgreSQL and MySQL, and the ActiveRecord work by @tblanchard changing Glorp itself, there are enough moving parts to necessitate setting up CI to ensure tests are always green.

Drive DescriptorSystem creation entirely from database schema and naming conventions

Rais ActiveRecord manages to derive most mappings from the database schema via naming conventions eg "Convention over Configuration".

There is no reason Glorp cannot do the same. This ability would make it easier to embrace existing database schemas and allow Pharo to build new applications atop old databases with much less effort.

It could also make it potentially easier to migrate from one database platform to another given good DDL generation from the table model.

SQLite3 platform needs some more configuration to pass more tests.

A number of tests are fixed by defining method maximumQueryValueSize and returning 50000.

This is the largest string SQLite can handle in a like or glob expression and, lets be real, one isn't likely to be querying with parameters this large.

See https://sqlite.org/limits.html

"The pattern matching algorithm used in the default LIKE and GLOB implementation of SQLite can exhibit O(Nยฒ) performance (where N is the number of characters in the pattern) for certain pathological cases. To avoid denial-of-service attacks from miscreants who are able to specify their own LIKE or GLOB patterns, the length of the LIKE or GLOB pattern is limited to SQLITE_MAX_LIKE_PATTERN_LENGTH bytes. The default value of this limit is 50000. A modern workstation can evaluate even a pathological LIKE or GLOB pattern of 50000 bytes relatively quickly. The denial of service problem only comes into play when the pattern length gets into millions of bytes. Nevertheless, since most useful LIKE or GLOB patterns are at most a few dozen bytes in length, paranoid application developers may want to reduce this parameter to something in the range of a few hundred if they know that external users are able to generate arbitrary patterns."

Also need to define autoTrimsStringsLongerThanColumnSize to return true. It doesn't really trim strings. SQLite will let you put a string of arbitrary length in any field type and it does not constrain inputs like other dbs. But the tests use this to determine whether to expect an error to be thrown if an oversized string is set. SQLite does not throw an error, it takes whatever you give it.

Finally, I went ahead and defined sqlTextCurrentServerUTCTimestamp because despite not having date and time types (use strings), it does have functions for manipulating date and time types, but always returns formatted strings.

RelationExpression>>primaryKeyFromDictionary: can't find primaryKey for descriptors with FilteredTypeResolver

Introduction

When trying to look into the cache instead of performing a database query, there is a check to verify if the referenced object primary key is already in the cache, to get the value used as index, the primaryKeyFromDictionary: aDictionary is called which will return the value or nil.

If you use a Descriptor that uses a FilteredTypeResolver, the queries you perform will use a IN(...) query together with the pk value.

E.g. If have this hierarchy:

Participant   Type identifier
  \_ Player     'player'
  \_ Team      'team'

So when I perform a read on Participant the query will do SELECT ... FROM Participant WHERE type IN ('player', 'team').

But if in another Descriptor (e.g. for ParticipantRegistration) I have a ReferenceMapping to Participant or any of its subclasses, when performing a query like this:

aSession read: ParticipantRegistration where: [:each | each participant = aParticipant ]

Then the SQL generated will be like the following:

SELECT ... FROM ParticipantRegistration WHERE type IN ('player', 'team') AND participant_id = 10;

Description

Enter RelationExpression>>primaryKeyFromDictionary:.

This method tries to get the actual primary key from the relation expression, but since GLORP is prepared to have multi column primary keys that it concatenates to build keys for different purposes it has a special check to know if the expression is an AND kind of relation, meaning that the PK might be composed by more than one field.

The problem is that this check is ignoring the possibility of expressing something like the FilteringTypeResolver type column AND the actual PK (single value), which is the most common case.

As follows:

RelationExpression>>primaryKeyFromDictionary: aDictionary
	"Given a set of parameters, return a primary key suitable for retrieving our target. 
        Do this only if the expression is for a primary key, and has no other conditions than
        the primary key one.  If the table's primary key is composite, return the array that will 
        be needed with the found values in the right position and nils elsewhere.  
        (If unreferenced primaryKey fields are nillable, this could return a matching key. 
         A query with other values elsewhere will throw away the primary key, returning nil.  One without will "

	| left right field primaryKeyFields |
	relation = #AND
          ifTrue: [
             left := leftChild primaryKeyFromDictionary: aDictionary.
             left isNil ifTrue: [^nil].
             right := rightChild primaryKeyFromDictionary: aDictionary.
             right isNil ifTrue: [^nil].
            ^self assembleCompositePrimaryKeyFrom: left and: right].
	relation = #= ifFalse: [^nil].
        "method continues"

That relation = #AND condition there ignores the case that the #AND relation might be used to specify the filtered type identifier and the actual PK value.

So I quickly changed that to this variation, also checking for the option of having an #IN kind of relation in the left side of the expression:

	| left right field primaryKeyFields |
	relation = #AND
		ifTrue: [ left := leftChild primaryKeyFromDictionary: aDictionary.
			right := rightChild primaryKeyFromDictionary: aDictionary.
			"Assume this might be filtered type resolver."
			^leftChild relation == #IN
				ifTrue: [ right  ]
				ifFalse: [ left isNil | right isNil
						ifTrue: [ nil ]
						ifFalse: [ self assembleCompositePrimaryKeyFrom: left and: right ] ] ].
	relation = #= ifFalse: [^nil].
        "method continues"

This fixed the issue and as a side effect got a tremendous speedup in my program, because now the cache is hit most of the times, avoiding to re-read the object from the database and then update the cache again, to be matched only when reading the object outside of a relation expression (it is, only when reading the object directly).

Comments

I'm creating the issue because a proper test case should be created to consider this bug solved, and to work as a heads-up to anybody already having cache issues with Descriptors using a FilteredTypeResolver .

testCamelToUnderscoreWithoutReverse fails on Pharo 8

#########################

1 tests did not pass:

#########################

GlorpInflectorTest
โœ— #testCamelToUnderscoreWithoutReverse (1002ms)
TestFailure: Got 'free_b_s_d' instead of 'free_bsd'.
GlorpInflectorTest(TestAsserter)>>assert:description:resumable:
GlorpInflectorTest(TestAsserter)>>assert:description:
GlorpInflectorTest(TestAsserter)>>assert:equals:
at least on Pharo 8

Wrong lincense - should be LGPL (modified)

This repository mentions Glorp to be licensed under the MIT. According to the documents in VW, it is not correct. The right license is LGPL with some clarifications for usage in Smalltalk:

This is a Smalltalk library, licensed under the LGPL. However, It is not
obvious how some of the terms and concepts in the license should
be sensibly applied to Smalltalk. The various Smalltalk image models often
do not directly correspond to the ideas of programs and libraries
that are linked to form executables. We, the authors, would like to clarify
our interpretation of the LGPL as it applies to Smalltalk, and what we 
permit you to do with this code. We use the term LGPL(S) to indicate the use
of the LGPL, but with these clarifications.

This code is intended to be usable as a library, without the intention to 
restrict the license of the program that uses it. Thus, you may use this library
the same way you would normally use any other Smalltalk library. That is, 
you may load it into an image or otherwise make it available for use in whatever
ways are appropriate to the Smalltalk implementation you are using (including,
but not limited to file-in, linking a shared library, or loading a binary 
representation such as a parcel,  BOSS file, image segment or image component).
You may write code that uses the library, including subclassing library classes
and having the library call back to your code using blocks, the #perform: 
mechanism, or similar mechanisms. You may use this code,  including creating
and distributing packaged images, libraries, development images and executables
that include the library code. We do not consider these activities sufficient
to make the entire program/image/executable or any portion of it beyond the
library itself be considered a derivative work, and in any case we place no
restrictions on what licenses you may use for code that uses this library in
these or similar manners.

If, however, you modify the class definitions or methods of the library, we do
consider those modified sections a derivative work, and as such they are fully subject
to the restrictions described in the LGPL. Basically, you'll need to release the
source of any modifications.

If you require any further clarification, we'd be happy to provide it. You can contact
the authors c/o Alan Knight, [email protected].

The full text of the LGPL license is included below.

  GNU LESSER GENERAL PUBLIC LICENSE
       Version 2.1, February 1999

 Copyright (C) 1991, 1999 Free Software Foundation, Inc.
     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL.  It also counts
 as the successor of the GNU Library Public License, version 2, hence
 the version number 2.1.]

    Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

  This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it.  You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.

  When we speak of free software, we are referring to freedom of use,
not price.  Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.

  To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights.  These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.

  For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you.  You must make sure that they, too, receive or can get the source
code.  If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it.  And you must show them these terms so they know their rights.

  We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.

  To protect each distributor, we want to make it very clear that
there is no warranty for the free library.  Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.

  Finally, software patents pose a constant threat to the existence of
any free program.  We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder.  Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.

  Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License.  This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License.  We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.

  When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library.  The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom.  The Lesser General
Public License permits more lax criteria for linking other code with
the library.

  We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License.  It also provides other free software developers Less
of an advantage over competing non-free programs.  These disadvantages
are the reason we use the ordinary General Public License for many
libraries.  However, the Lesser license provides advantages in certain
special circumstances.

  For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard.  To achieve this, non-free programs must be
allowed to use the library.  A more frequent case is that a free
library does the same job as widely used non-free libraries.  In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.

  In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software.  For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.

  Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.

  The precise terms and conditions for copying, distribution and
modification follow.  Pay close attention to the difference between a
"work based on the library" and a "work that uses the library".  The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.

  GNU LESSER GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".

  A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.

  The "Library", below, refers to any such software library or work
which has been distributed under these terms.  A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language.  (Hereinafter, translation is
included without limitation in the term "modification".)

  "Source code" for a work means the preferred form of the work for
making modifications to it.  For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.

  Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.
 
  1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.

  You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.

  2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) The modified work must itself be a software library.

    b) You must cause the files modified to carry prominent notices
    stating that you changed the files and the date of any change.

    c) You must cause the whole of the work to be licensed at no
    charge to all third parties under the terms of this License.

    d) If a facility in the modified Library refers to a function or a
    table of data to be supplied by an application program that uses
    the facility, other than as an argument passed when the facility
    is invoked, then you must make a good faith effort to ensure that,
    in the event an application does not supply such function or
    table, the facility still operates, and performs whatever part of
    its purpose remains meaningful.

    (For example, a function in a library to compute square roots has
    a purpose that is entirely well-defined independent of the
    application.  Therefore, Subsection 2d requires that any
    application-supplied function or table used by this function must
    be optional: if the application does not supply it, the square
    root function must still compute square roots.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.

In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library.  To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License.  (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.)  Do not make any other change in
these notices.

  Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.

  This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.

  4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.

  If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.

  5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library".  Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

  However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library".  The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

  When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library.  The
threshold for this to be true is not precisely defined by law.

  If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work.  (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

  Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

  6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

  You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License.  You must supply a copy of this License.  If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License.  Also, you must do one
of these things:

    a) Accompany the work with the complete corresponding
    machine-readable source code for the Library including whatever
    changes were used in the work (which must be distributed under
    Sections 1 and 2 above); and, if the work is an executable linked
    with the Library, with the complete machine-readable "work that
    uses the Library", as object code and/or source code, so that the
    user can modify the Library and then relink to produce a modified
    executable containing the modified Library.  (It is understood
    that the user who changes the contents of definitions files in the
    Library will not necessarily be able to recompile the application
    to use the modified definitions.)

    b) Use a suitable shared library mechanism for linking with the
    Library.  A suitable mechanism is one that (1) uses at run time a
    copy of the library already present on the user's computer system,
    rather than copying library functions into the executable, and (2)
    will operate properly with a modified version of the library, if
    the user installs one, as long as the modified version is
    interface-compatible with the version that the work was made with.

    c) Accompany the work with a written offer, valid for at
    least three years, to give the same user the materials
    specified in Subsection 6a, above, for a charge no more
    than the cost of performing this distribution.

    d) If distribution of the work is made by offering access to copy
    from a designated place, offer equivalent access to copy the above
    specified materials from the same place.

    e) Verify that the user has already received a copy of these
    materials or that you have already sent this user a copy.

  For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it.  However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.

  It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system.  Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.

  7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:

    a) Accompany the combined library with a copy of the same work
    based on the Library, uncombined with any other library
    facilities.  This must be distributed under the terms of the
    Sections above.

    b) Give prominent notice with the combined library of the fact
    that part of it is a work based on the Library, and explaining
    where to find the accompanying uncombined form of the same work.

  8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License.  Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License.  However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.

  9. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Library or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.

  10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.

  11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all.  For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded.  In such case, this License incorporates the limitation as if
written in the body of this License.

  13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number.  If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation.  If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.

  14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission.  For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this.  Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.

    NO WARRANTY

  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.

     END OF TERMS AND CONDITIONS

           How to Apply These Terms to Your New Libraries

  If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change.  You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).

  To apply these terms, attach the following notices to the library.  It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

    <one line to give the library's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This library is free software; you can redistribute it and/or
    modify it under the terms of the GNU Lesser General Public
    License as published by the Free Software Foundation; either
    version 2.1 of the License, or (at your option) any later version.

    This library is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public
    License along with this library; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the
  library `Frob' (a library for tweaking knobs) written by James Random Hacker.

  <signature of Ty Coon>, 1 April 1990
  Ty Coon, President of Vice

That's all there is to it!

Various cleanups

  • abstract class AbstractProxy should return true for #isAbstract

  • align init protocols
    -- AbstractProxy>>#instVarAt: should be in "accessing" and not "initialize-release"
    -- AbstractProxy>>#proxyInitialize should be in "initialization" method category and not "initialize-release"
    -- AdHocProxy>>#proxyInitialize should be in "initialization" method category and not "initialize"

  • abstract class ElementBuilder should return true for #isAbstract

  • abstract class Query should return true for #isAbstract

  • abstract class AbstractReadQuery should return true for #isAbstract

  • abstract class GlorpDatabaseType should return true for #isAbstract

  • abstract class GlorpAbstractNumericType should return true for #isAbstract

  • abstract class GlorpAbstractIntegerType should return true for #isAbstract

  • abstract class GlorpAbstractStringType should return true for #isAbstract

  • add missing class comment to GlorpJSONType, GlorpJSONBType, GlorpPGArrayType, GlorpBinaryType, GlorpUUIDType

  • fix terminating period in method signature lint issue in ActiveRecordDescriptorSystem class>>#sessionForAccessor:

  • fix isNil ifTrue: -> ifNil: and isNil ifFalse: -> ifNotNil: lint issue in ActiveRecordDescriptorSystem>>#sessionForLogin:

  • put ActiveRecordInflector>>#initializeIrregular, initializePlural, initializeSingular, initializeUncountable into "private-initialization"

  • remove unnecessary dots at end of method and apply formatting

  • ActiveRecordDescriptorSystem>>#rootClass should not hardcode ActiveRecordModel but use #defaultRootClass

  • fix lint in ActiveRecordDescriptorSystem>>#allClasses

  • ActiveRecordDescriptorSystem>>#initialize should not hardcode ActiveRecordQuery but use #defaultQueryClass

  • #constructAllClasses and #constructAllTables should not be in initialization protocol (for full hierarchy)

  • DescriptorSystem>>#initialize should be in "initialization"

  • ActiveRecordDescriptorSystem>>#initialize should be in "initialization"

  • ban lint in ActiveRecordDescriptorSystem>>#tableClassForClass:

  • move some methods in ActiveRecordDescriptorSystem from "private" to "private - initialization"

  • format comment in ActiveRecordDescriptorSystem>>#initializeTable: to fit Pharo tool fonts

  • correctly categorize AddingWriteStream class>>#on:

  • categorize or delete Cache>>#initialize

  • lint clean CacheManager>>#hasExpired:

  • chaining in CompoundSelectCommand>>#printSQL

  • chaining in DatabaseAccessor>>#logOnlyOn:

  • fix lints in DatabaseAccessor>>#cursorFor:command:

  • chaining in DatabaseAccessor>>#endLogging

  • lint in DatabaseAccessor>>#initialize

  • categorize DatabaseAccessor

  • cascade in FixedSizeQueue>>#printOn:

  • review GlorpSession>>#cacheContainsObject:

  • move deprecations into own package (GlorpSession>>#readManyOf:)

  • fix DelegatingDatabaseConverter class side messages

Unsupported drivers for SQLServerPlatform?

When I do following

login := Login new
database: SQLServerPlatform new;
username: 'name';
password: 'secret';
host: 'localhost';
port: '1433';
databaseName: 'mydb'.
accessor := DatabaseAccessor forLogin: login.
accessor login.

It complains about SQLServerPlatform drivers not installed.
What can I do to fix it?

Suggestion for fixing 'Instance of DescriptorSystem did not understand #inflector' error

In attempt to establish connection to the database, when sessionForLogin message is sent to DescriptorSystem class, following error occurred: 'Instance of DescriptorSystem did not understand #inflector'. The cause of this error is sending inflector message inside joinFor: toTables: fromConstraints: toConstraints: method to DescriptorSystem itself despite the fact that inflector message is not implemented in DescriptorSystem.
After further browsing the code I realised that inflector is present inside ActiveRecordDescriptorSystem (the subclass of DescriptorSystem) as instance variable (with getter and setter) so I decided to move it to the instance variables of DescriptorSystem, create getter and setter and instantiate it inside initialization method (inflector := ActiveRecordInflector new.). After that, everything worked fine. I thought that this information may be valuable for you either as fix for the described problem or a hint for some better solution. :)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.