SQL_Latin1_General_Cp850_BIN

I think you might be missing a call to #initializeFunctions, which is particularly needed for playing with the info schema. This works with 2008 native client:

sqlsrvrLogin :=   (Login new)

                                database: (SQLServerPlatform new initializeFunctions);

                                username: 'sa';

                                password: 'dw29558';

                                secure: false;

                                schema: 'dbo';

                                connectString: 'sql_2008_native'.

GlorpDatabaseLoginResource defaultLogin: sqlsrvrLogin.

"GlorpDatabaseLoginResource reset.

GlorpDemoTablePopulatorResource invalidateSetup.

ActiveRecord defaultLogin: (GlorpDatabaseLoginResource current login)"

accessor := Glorp.DatabaseAccessor forLogin: sqlsrvrLogin.

accessor login.

session := Glorp.GlorpSession new.

session system: (Glorp.SQLServerMetadataDescriptorSystem forPlatform: sqlsrvrLogin database).

session accessor: accessor.

(query := Glorp.Query readManyOf: Glorp.DatabaseTable where: [:each | each

schema os_Equal: 'dbo']) setOrdering: #(#name).

query executeIn: session.

Results: #(a Glorp.DatabaseTable(dbo.MSreplication_options) a Glorp.DatabaseTable(dbo.spt_fallback_db) a Glorp.DatabaseTable(dbo.spt_fallback_dev) a Glorp.DatabaseTable(dbo.spt_fallback_usg) a Glorp.DatabaseTable(dbo.spt_monitor) a Glorp.DatabaseTable(dbo.spt_values) a Glorp.DatabaseTable(dbo.test_large_array_binding) a Glorp.DatabaseTable(dbo.test_large_array_binding3) a Glorp.DatabaseTable(dbo.testAnswerStream))

Well, you've got SCHEMA misspelled in the error message, but assuming that's just a typo, then that seems like it should reasonably work. SQL Server did at some point make some changes to INFORMATION_SCHEMA that might be an issue, but I suspect more likely it's just not finding the tables. I doubt that the sort order is significant, I suspect it just isn't looking in the right place for those tables.

Armin,

Sorry, I forgot that you are using OS, so my VW-based answer is probably not relevant. In fact, that init call may be redundant these days, too!

- Dave

I think you might be missing a call to #initializeFunctions, which is particularly needed for playing with the info schema. This works with 2008 native client:

sqlsrvrLogin :=   (Login new)

                                database: (SQLServerPlatform new initializeFunctions);

                                username: 'sa';

                                password: 'dw29558';

                                secure: false;

                                schema: 'dbo';

                                connectString: 'sql_2008_native'.

GlorpDatabaseLoginResource defaultLogin: sqlsrvrLogin.

"GlorpDatabaseLoginResource reset.

GlorpDemoTablePopulatorResource invalidateSetup.

ActiveRecord defaultLogin: (GlorpDatabaseLoginResource current login)"

accessor := Glorp.DatabaseAccessor forLogin: sqlsrvrLogin.

accessor login.

session := Glorp.GlorpSession new.

session system: (Glorp.SQLServerMetadataDescriptorSystem forPlatform: sqlsrvrLogin database).

session accessor: accessor.

(query := Glorp.Query readManyOf: Glorp.DatabaseTable where: [:each | each

schema os_Equal: 'dbo']) setOrdering: #(#name).

query executeIn: session.

Results: #(a Glorp.DatabaseTable(dbo.MSreplication_options) a Glorp.DatabaseTable(dbo.spt_fallback_db) a Glorp.DatabaseTable(dbo.spt_fallback_dev) a Glorp.DatabaseTable(dbo.spt_fallback_usg) a Glorp.DatabaseTable(dbo.spt_monitor) a Glorp.DatabaseTable(dbo.spt_values) a Glorp.DatabaseTable(dbo.test_large_array_binding) a Glorp.DatabaseTable(dbo.test_large_array_binding3) a Glorp.DatabaseTable(dbo.testAnswerStream))

Well, you've got SCHEMA misspelled in the error message, but assuming that's just a typo, then that seems like it should reasonably work. SQL Server did at some point make some changes to INFORMATION_SCHEMA that might be an issue, but I suspect more likely it's just not finding the tables. I doubt that the sort order is significant, I suspect it just isn't looking in the right place for those tables.